Comments on: ELisp best practices? http://andreasjacobsen.com/2009/01/07/elisp-best-practices/ Another cause of procrastination Fri, 02 Jul 2010 06:05:30 +0000 hourly 1 http://wordpress.com/ By: The Betacantrips Travelogue » Emacs Lisp Best Practices? http://andreasjacobsen.com/2009/01/07/elisp-best-practices/#comment-156 The Betacantrips Travelogue » Emacs Lisp Best Practices? Sat, 24 Apr 2010 23:39:41 +0000 http://andreasjacobsen.com/?p=89#comment-156 [...] one page wondering the same thing. There’s always a ton of interesting stuff whenever you go poking at emacs packages; most [...] [...] one page wondering the same thing. There’s always a ton of interesting stuff whenever you go poking at emacs packages; most [...]

]]> By: Andreas http://andreasjacobsen.com/2009/01/07/elisp-best-practices/#comment-83 Andreas Thu, 08 Jan 2009 14:04:33 +0000 http://andreasjacobsen.com/?p=89#comment-83 That's interesting. I think autoload is next up on the list of things to add for my config. I did something similar previously, having a custom package of my own to require so I could gather any customizations there. I cut down on it when I realized I had a bunch of these where the only thing they did was require the original package. That’s interesting. I think autoload is next up on the list of things to add for my config. I did something similar previously, having a custom package of my own to require so I could gather any customizations there. I cut down on it when I realized I had a bunch of these where the only thing they did was require the original package.

]]> By: Chris http://andreasjacobsen.com/2009/01/07/elisp-best-practices/#comment-82 Chris Thu, 08 Jan 2009 12:59:29 +0000 http://andreasjacobsen.com/?p=89#comment-82 I have another way of doing it that may be more modular. When I want to use a new package, I make a new file ~/.emacs.d/me-package.el I put (require 'package) in me-package.el, along with any customizations for the package that I want. I then use autoload in my ~/.emacs to load me-package whenever I use one of the commands that the package provides. For example, I just started using ack instead of grep. I put (require 'ack) (setq ack-guess-type t) (setq ack-command "ack-grep --nocolor --nogroup") (provide 'me-ack) in ~/.emacs.d/me-ack and (autoload 'ack "me-ack" "grep replacement" t) in ~/.emacs I think the advantage of this is to separate the configuration of different packages, while not dying if one of the packages isn't present. It should also speed up initial loading time a little bit because large packages aren't loaded until they are needed. I have another way of doing it that may be more modular. When I want to use a new package, I make a new file ~/.emacs.d/me-package.el I put (require ‘package) in me-package.el, along with any customizations for the package that I want. I then use autoload in my ~/.emacs to load me-package whenever I use one of the commands that the package provides.

For example, I just started using ack instead of grep. I put

(require ‘ack)

(setq ack-guess-type t)
(setq ack-command “ack-grep –nocolor –nogroup”)

(provide ‘me-ack)

in ~/.emacs.d/me-ack and

(autoload ‘ack “me-ack” “grep replacement” t)

in ~/.emacs

I think the advantage of this is to separate the configuration of different packages, while not dying if one of the packages isn’t present. It should also speed up initial loading time a little bit because large packages aren’t loaded until they are needed.

]]>