Jeff Mincy <jeff(a)delphioutpost.com> writes:
>> When playing around with new features that I run across I
often
>> wind up starting to type M-x require <feature>, before I remember
>> that require is not interactive. Things like feature and require
>> that deal with the lisp 'environment' should be interactive.
>> maybe.
>
> Use `M-x load-file' and `M-x load-library' which accept strings and
> are meant to be interactive.
Yea, except that load-library doesn't test to see if you have already
loaded the file.
But when using interactively, one usually *doesn't* want that kind of
check.
better idea to load the features like (require 'mic-paren) rather
than
(load-library "mic-paren") so that you don't reload files
needlessly.
Sure, but that's not interactive use. Note that I didn't say, "use
(load-library ...)". I said, "use M-x load-library ...".
It just doesn't occur to me to mentally shift over to using
load-library for interactive usage
I'm afraid such shifts are sometimes necessary because of the
different nature of interactive and noninteractive use. Something
like the famous next-line -> forward-line difference.