[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inexplicable flaw: non-overridable .emacs

From: kj
Subject: Re: Inexplicable flaw: non-overridable .emacs
Date: Sat, 17 Mar 2007 13:43:58 +0000 (UTC)
User-agent: nn/6.7.2

In <address@hidden> Eli Zaretskii <address@hidden> writes:

>> From: kj <address@hidden>
>> Date: Thu, 15 Mar 2007 18:15:15 +0000 (UTC)
>> Please correct me if I'm wrong, it is my understanding that one
>> cannot use a command-line switch to tell emacs to read a config
>> file *other* than the standard ~/.emacs.

>You are only partly wrong: Emacs has a --load command-line switch that
>would load any file you name.  But such loading is not 100% equivalent
>to how Emacs loads a .emacs file, because .emacs is read at a certain
>point during the Emacs session startup, while files given via --load
>are read at a different point.  So the effects could be subtly
>different, especially with respect to display setup.

That's good to know, thanks, but, again, I'm puzzled: why would
Emacs treat ~/.emacs differently from a user-specified alternative?
It seems perversely unaccommodating on Emacs' part (even if only
in a passive-agressive sort of way :)  )

>Could you please tell why you don't want to have a .emacs file?

Nothing against an .emacs file, but occasionally I want to run
Emacs with a drastically different set of customizations from what's
in my .emacs file.  Since a lot of these customizations pertain
display, I need to do some experimentation to determine whether
the --load option will do what I need. 

NOTE: In my address everything before the first period is backwards;
and the last period, and everything after it, should be discarded.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]