🚀 go-pugleaf

In article <1991Apr16.170934.11292@athena.mit.edu> bjaspan@ATHENA.MIT.EDU (Barr3y Jaspan) writes:

   I would argue that "making the command permanent" is not something
   emacs lisp code should try to do.  All it is going to do is add a
   sexp to the end of the user's .emacs file, and that isn't always
   appropriate.  (For example, my .emacs is a symlink to emacs.elc,
   which is a compiled form of my emacs.el.  Adding something to the
   end of emacs.elc would be the wrong choice since it will get blown
   away next time I compile emacs.el.)

I don't agree that adding code to the end of your .emacs is too
fragile.  It assumes that your .emacs exists or is creatible, has
valid lisp code in it, and doesn't get wiped out except under the
user's control, and it preserves these assumptions.

Instead of removing a feature that seems to work well for the majority
of Emacs users, I would rather expect those users who have set up
unusual configurations to solve the problems their changes introduce.
I mean, if your .emacs is so big it should be compiled, can't you put
the enabling clauses in your .emacs.el yourself?

Perhaps instead of a symbolic link, your .emacs could ("load "~/.emacs").

-JimB
--

-Jim Blandy
jimb@ai.mit.edu