Irreal

The other day, I wrote about Michael Behr’s scientific writing workflow that is centered around Zotero, Emacs, and Org mode. Here’s another example of a Zotero workflow, this time from Nick Judd.

Like Behr, Judd collects and manages reference papers with Zotero. Unlike Behr, he prefers to write his own papers in Markdown and use Pandoc to export the result to a PDF through \(\LaTeX\) rather than use Org mode. He doesn’t explain his choice—he doesn’t even mention Org—but his workflow seems to work well for him and, of course, Markdown/Pandoc is a more universal solution than Org mode.

If Markdown makes more sense for you, be sure to take a look Judd’s post to see how he ties everything together. He has detailed directions for getting everything installed and configured. Like Behr, he uses the Emacs package Zotxt to interact with Zotero from within Emacs. And if you haven’t seen Muad Abd El Hay’s comment to my Behr post, take a look at that too. Hay describes a slightly different Zotero workflow that uses John Kitchin’s org-ref package to handle the citations. It looks like an excellent solution.

Tycho Garen has an interesting use case. Because he uses a single laptop to work on many projects, he wanted a way to have separate Emacs instances so that his buffers don’t get mixed up between projects. That’s easy enough to do by simply invoking multiple Emacs instances but then if his X-Windows dies he loses everything. As Sacha told us, the way to avoid that is to run Emacs in daemon mode. But how can you run multiple Emacs instances in daemon mode?

Garen has the answer. His solution involves having emacsclient connect to the server with TCP. Follow the link for the details. One of the commenters points out that this can be a security problem if external users can reach the socket. Stefan Monnier replied that there’s a secret key in the server file so the security problem isn’t as bad as it sounds but in any event you can still use local Unix sockets by specifying --socket-name rather than --server-file as an option to emacsclient. This is explained (sort of) in the emacsclient options section of the Emacs manual.

Garen shows another nice trick in his post. I often see people starting the Emacs daemon at boot time by messing with systemd or whatever their system uses to control the boot process. Garen simply makes use of the fact that crontab has a @reboot “time” that will perform the action when the system boots. That solves the problem nicely and easily. Again, see his post for the details.

Most of us probably won’t have occasion to need multiple Emacs instances but it’s nice to know how to do it in case the need does arise.

If you tend to obsess over the number of open Emacs buffers, worrying about performance, here’s some good news

"Operation finished; killed 543 buffers"

There's about 400 left still. #Emacs at 29+ days uptime. Still snappy and responsive.

— Gergely Nagy (@algernoone) December 1, 2016

I’ve never come close to that many buffers and I don’t know what his machine configuration is like but you have to admit that that’s pretty impressive.

When I first started using Emacs, one of the ways I learned about useful configuration settings and emacs-lisp was to read other people’s emacs configurations. Oddly, I’m still reading them today. When I read an expert’s configuration, I almost always learn something new and useful.

It’s easy to find configurations with a simple DuckDuckGo (or Google, if you must) search but caisah has curated a list of nice emacs configurations. You’ll recognize many of the people these configurations belongs to (Sacha Chua, Magnar Sveen, John Wiegley and Oleh Krehel to name just four) so you can be sure of learning some useful configuration settings and elisp tricks by reading them.

Besides the opportunity to learn some configuration items worth stealing, I find reading the configurations and seeing how other people have solved their editing problems enjoyable even if I don’t need the particular feature under discussion for my own workflow. If you feel the same way, bookmark caisah’s list and use it to check out a configuration or two when you have a few minutes.

Sometimes you want to move a file you have open in Emacs. More often, perhaps, you simply want to rename the file. Emacs has some functions that do this but none of them are entirely satisfactory. The write-file function comes close but it leaves the old file in place and the rename functions don’t take care of the buffer. Zachary Kanfer has an interesting bit of Elisp that does the right thing.

His code copies the file to a new location (or name) using write-file so that the buffer name is changed and any changes later saved will be written to the new file. If the move is successful, the old file is deleted.

This seems pretty simple and it is but it’s surprising how often it comes up. If you find yourself in this situation more than once it’s probably worth your while to add Kanfer’s code to your init.el.