Re: [O] [OT] Requiring packages which may be missing?

Tim Cross writes: > You do need to be careful when sharing your .emacs.d between machines to > ensure you use something like gitignore to exclude things you may not > want to share across systems (such as auto-save files, various command > history files etc). Yes, that's

Re: [O] [OT] Requiring packages which may be missing?

You do need to be careful when sharing your .emacs.d between machines to ensure you use something like gitignore to exclude things you may not want to share across systems (such as auto-save files, various command history files etc). I've found the use of use-package and init.el in a git repo the

Re: [O] [OT] Requiring packages which may be missing?

Have a look at the use-package package. I have found it makes this much easier. There are some complications associated with using it and org-mode, due mainly to emacs being bundled with one version and another vesion being available in both the gnus and org-mode elpa repos. However, once you

Re: [O] [OT] Requiring packages which may be missing?

I find that the best way is to store the entire ~/.emacs.d directory (including the /elpa subdirectory) in a git repository. This makes it easy to keep your entire config in sync between machines, and it means you keep your init file in sync with the versions of packages. Otherwise you may find

[O] [OT] Requiring packages which may be missing?

Hi, This is more of a general emacs question. I often use the same .emacs on various machines which may not have all the packages I normally load. To get around this I use the Fabrice Niessen's 'try-require' function taken from http://www.mygooglest.com/fni/dot-emacs.html Due to some recent