Christmas stories

I’m sure every family has a collection of stories they share around Christmas. One of the favorites in my mom’s family is about the time, when my mom was in elementary school, her dad told her they weren’t having Christmas so that she would stop bugging them about her presents. He told her they couldn’t afford Christmas that year.

My mom told her teacher that they weren’t having Christmas because they didn’t have any money. So, my mom was allowed to drag the classroom tree home, and apparently it was a sad, pitiful thing. Grandma and Grandpa didn’t understand why the teacher gave the tree to my mom.

They didn’t understand later, either, when various church and charity groups from around Flint brought baskets of food and gifts to their house. And, despite my Grandma’s protestations that they didn’t need charity, everyone insisted they accept the goods because everyone deserves to have Christmas.

Eventually, they figured out what had happened.

Customizing Emacs

I figure one way to become more familiar with Emacs is to customize some of its settings. Of the various pages I’ve found on the web that describe different customizations, I’ve found these two to be the most useful.

First, I wandered around the Emacs customization menu by clicking the Customize Setup link on the original home screen. There were so many options there that it was a bit overwhelming, even if you browse using the M-x customize-browse command. I did use the menu to “Save for future sessions,” which created a virtually empty .emacs file for me. I figured that way the file would be saved in the correct place (i.e., my home directory).

Next, I thought I’d browse the options for changing the color scheme. These instructions were the most helpful for installation. Once installed, I typed M-x color-theme-select and then clicked/RET on the different themes until I found one I liked. Not too complicated. Seems you can customize your own theme using this tool, too.

I poked around online and found several examples of .emacs.el or init.el files. (Seems like it’s a “thing” to post your Emacs customizations online…. kind of like the equivalent of a g33k bicep flex.) I also read more about the pros/cons of Emacs vs. WinEdt. It seems like one of the big cons of Emacs for Windows users is that several of the keyboard shortcuts and/or default behaviors are so different in Emacs that it creates problems if you’re moving back and forth across tools. Sure, you could customize Emacs to get rid of some of those annoying default behaviors, but, boy, does that seem like a lot of work. And, while it’s easy in linux to install packages from the command line, in Windows it’s a several step process.

What I’ve learned so far? I could be a super g33k and use Emacs if I really wanted to, but I’m not sure I really want to. As far as tools for writing and editing text files (research articles and R or Stata code) go, there are a range of options from g33kiest (Emacs+AUCTeX, with apologies to Chris) to smart but pragmatic g33k (WinEdt) to lazy g33k (LyX, with apologies to Justin) to least g33k (MSWord). [Actually, I guess a real geek would write LaTeX so natively they could just use Notepad2, or heavens forbid, the notepad that comes with Win. Or, I guess a real geek would be using a linux box anyway, but I digress…]

So, while I am confident I could learn to use Emacs, and maybe it really would be transformative and change my life forever, but I think I’m going to be more pragmatic and move on to WinEdt for now.

Updated to add: FWIW, I’ve saved the most useful pages about setting up Emacs on Windows to my delicious.

Follow-up to post about LaTeX, etc.

Yesterday, I provided a rough outline of the steps for installing Emacs + AUCTeX in Windows 7.

Upon further reflection, I realized a few things about the process. First, most of the documentation for these tools is outdated and/or poorly written (at least for recent versions of Windows). Second, it’s way easier to install this stuff than the documentation would lead you to believe. Third, using the software itself is also way easier than the documentation would lead you to believe or than you might think yourself.

Specific examples?

Installing Emacs in Windows 7 is a three step process: Download file. Unzip file into preferred directory (e.g., C:\Program Files\emacs\). Set the HOME property to point to %USERPROFILE%.

Installing AUCTeX? Download file. Unzip file into the Emacs directory (above). However, if you read the AUCTeX manual, you’d think this was a 30 step process.

Everything seems to work ok. AUCTeX loads when a .tex file is being edited, and works. This setup even comes with a spell checker already installed, even though some of the [outdated] online documentation would lead you to believe that you have to install one separately. Perhaps its broken in a way I’m too n00bish to recognize, but so far, so good.

I went through the Emacs tutorial and the first 2 of these tutorials, and everything seemed pretty straightforward. These ref cards for AUCTeX and Emacs seem to have all the essentials. It’s just a matter of learning different keyboard shortcuts than the ones I’ve been using in Notepad2 or Word.

On the other hand, there’s this mystery .emacs file that is supposed to be where I put my personalized settings for using Emacs. I see an .emacs folder, but not a file. So, that’s a mystery to me, but I’m sure I can figure it out. So that’s the next step: Customize my environment, export my existing bibliography files to a .bib file, and see if I can create a custom formatting .bst, or whatever it’s called.

Installing and learning LaTeX

Long on my to-do list has been to use LaTeX, mainly for its BibTeX features. I’ve avoided it for so long because I’m pretty adept at MSWord. However, with Office2010 and that blasted ribbon, they broke all my keyboard shortcuts for menu items (imagine grumpy old professor shaking hand at the gods and yelling).

As a first step, I emailed Chris (not to be confused with this CL) to ask for suggestions, which he graciously provided. Then, having narrowed things to Emacs+AUCTex (Chris’s strategy) and WinEdt, I turned to FB, which yielded additional suggestions including Sublime Text and LyX. The latter is apparently a good GUI tool, but the exported raw .tex can be clunky according to those who have used it. (I imagine it’s not unlike creating a webpage in Word, which you can do, but I wouldn’t recommend.)

I decided to install Emacs, LyX, and WinEdt, but I think I’m going to start with Emacs and try LyX and WinEdt when I inevitably get stuck.

Figuring out which version and how to install Emacs also took a bit of effort, particularly because a lot of the how-tos, which may include links to packages, aren’t necessarily always linking to the latest stable version. I found these instructions to be the clearest. However, I went to the original source for the install files. It seems that AUCTeX isn’t compatible with the most recent version of Emacs, so I had to go back and re-install Emacs. Typical (for me at least).

Here are the (abbreviated) steps I went through:
.5. Read several introductions to LaTeX, including some recommended by Chris.
1. Install MiKTeX.
2. Install WinEdt.
3. Install LyX. Since I already installed MiKTeX, I had to navigate to the tex.exe file in the miktex\bin\x64 folder during LyX install. It seemed to find and get all the missing packages and automatically install them in the correct MiKTeX directory (thank goodness).
4. Install latest version of Emacs.
5. Set HOME property.
6. Install version of Emacs that works with AUCTeX.

Next step(s): Check on spellchecking features, setup preferences, etc.

Edited to add: Here’s my first document. 😉

Things I have been thinking about

I’m trying to get back in the habit of posting here, even if it’s not super important, interesting, or research-related.

Yesterday, I submitted another small grant application for OPOSSEM. We need some MediaWiki development work done, and [surprise] I haven’t been able to find anyone able or willing to work for free. Hopefully, with some funds available, we can hire a firm to get the wiki-based textbook going. Also, I exchanged a flurry of emails this morning about next steps: including getting an official launch message out there, figuring out how to recognize and reward user contributions, and hopefully starting a project similar to the Wikipedia Ambassadors program, but for the OPOSSEM textbook. Of course, that will be easier once the programming is done on the MediaWiki site.

I also exchanged a round of emails with various folks about open-source publishing, not strictly OPOSSEM-related, but also in journals. It is apparently an issue that is percolating at the Canadian Federation for the Humanities and Social Sciences. A similar debate is going on in the U.S. Of course, there’s also the recent debate about Elsevier and their prices for bundled journal subscriptions. I don’t have anything to add here, but I do find the politics of this interesting. And, I do tend to think that much knowledge is publicly funded through university and targeted research funding, and therefore, the fruits of that funding should be a public good, as widely available as possible. However, faculty members tend to be a conservative bunch, and really it’s going to require academics to be a little less resistant to change and more open to new and different metrics of “quality” than whether a small number of gatekeepers at certain journals deem content to be of quality.

Finally, last week I learned something new about academic hiring practices in Canada, and I’ve been thinking about it a bit since we have a couple of on-going searches in our department right now. I knew that all academic ads in Canada include some language about first priority for Canadian (resident or citizen) applicants. Clearly, it’s not an insurmountable hurdle, since I got hired up here, and many others do as well. I had always assumed it was a sort of Canada-first employment policy that applied to all jobs. Turns out it’s not. It just (or mostly?) applies to academic jobs, which was explained to me by Daniel Béland during coffee chitchat during last week’s graduate student conference (awesome, BTW…. the US could stand to have more of these opportunities for grad students). In any event, I skimmed a couple of articles about the policy to supplement what Daniel told me, and now, I find it fascinating.

Short version: In the late 60s, a number of academics were worried about the influx of Americans into the Canadian academic job market, and [though I don’t know whether it was material or cultural interests driving it] they framed a movement around the effect this was having on the content (i.e., too much American sociology, not enough CanCon) of the curriculum in Canadian universities. In 1982, the movement successfully got a provision added to immigration law to protect academic jobs from non-Canadian academics. At least one article suggests that the movement had the effect of increasing CanCon in campus curricula in the social sciences.

I’m curious about the effect the law has on the Canadian academic job market, and also on the training of Canadian PhDs. Economists certainly would have one hypothesis about the effects of protectionism on an industry, but I wonder whether that applies here. And, of course, I wouldn’t really want to touch that debate directly with a 10 foot pole. My sense is that enough universities find ways around the law if they really want to, and there is a fundamental problem in Canada of not enough growth in tenure-track jobs to satisfy the number of PhDs we produce collectively (and I do think the academy has a collective responsibility to try to employ as many of the qualified individuals we train, or stop training them). So, it’s complicated. And, interesting. And that’s all I have to say about that. 😀