[mew-int 00932] Re: Relation between mew.el and .emacs
Tatsuya Kinoshita
tats at example.com
Fri Jun 28 07:49:08 JST 2002
In message [mew-int 00929], on Wed, 26 Jun 2002,
Charles Muller <acmuller at example.com> wrote:
> From what I can tell from the manual and what I read on the list,
> people seem to be keeping their Mew customizations in a "mew.el
> (or .mew)" file that resides in the user path (perhaps something
> like /home/chuck/lisp/mew.el [?] ).
.mew.el (not mew.el) is loaded from user's home directory.
(e.g. /home/chuck/.mew.el)
> Up to now, I have been adding all of my tweaks to my .emacs file,
> but if it is better to add them to a separate mew.el file, I
> would like to start doing that. Is that the right thing to do?
Yes. ~/.mew.el is loaded by Mew after Mew is loaded, so you can
use Mew's internal variables, functions, etc. It's useful.
For example, if the [mew-int 00918] configuration is put in
~/.emacs, it doesn't work, because mew-draft-body-map is not yet
defined. If you put it in ~/.mew.el, it works.
> If this is correct, then I would imagine that I will need to add
> a path statement to my .emacs file to point out the location of
> the customized "mew.el" file. If this is also correct, can show
> me how this statement should be formed?
The mew-rc-file variable is defined in mew-vars.el. If you want
to use "~/lisp/mew.el" instead of "~/.mew.el", put
(setq mew-rc-file "~/lisp/mew")
in your ~/.emacs.
--
Tatsuya Kinoshita
More information about the Mew-int
mailing list