From: Tim X <timx@nospam.dev.null>
Subject: Re: Multiple .emacs files
Date: Tue, 12 Sep 2006 12:03:00 +1000 [thread overview]
Message-ID: <87irjton8r.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: ud5a2c3vm.fsf@gmail.com
Mathias Dahl <brakjoller@gmail.com> writes:
> floyd@apaflo.com (Floyd L. Davidson) writes:
>
>>>I have played a bit with the -u option, but have yet to get it to work
>>>with a config file named .emacsT
>>
>> emacs -q -l ~/.emacsT
>
> A bit of a warning: I think I saw someone mentioning that doing the
> above was not exactly like switching your init file. What you do with
> the above is turn init file loading off and at the same time telling
> emacs to load another file. I am not sure but maybe things like
> Customize might not work as you expect (not saving to the .emacsT
> file).
>
> Someone who knows more can probably fill in here, or you can search
> the archives.
>
I have seen others report exactly this problem, so I think it is a
real concern. In particular, you may find that when you go to save
customize settings, it will fail or save it where you did not expect.
There is a variable that customize uses which may get around this
problem if you set it explicitly, but I seem to remember someone
reporting problems getting this to work as desired/expected.
There is a package out there called something like initz, which
provides a way of splitting up your emacs configuration so that only
certain parts are loaded depending on the emacs being run. I've not
used it myself, but am thinking about it as I'm now running two
different emacsen on a regular basis (emacs 21 and emacs 22 CVS) and
have come across some minor differences that will cause problems when
starting one of the emacsen. I don't know how well this will handle
the customize problem though.
HTH
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2006-09-12 2:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6688.1157814085.9609.help-gnu-emacs@gnu.org>
2006-09-09 15:25 ` Multiple .emacs files Floyd L. Davidson
2006-09-11 6:29 ` Mathias Dahl
2006-09-11 7:55 ` Floyd L. Davidson
2006-09-12 2:03 ` Tim X [this message]
2006-09-12 18:06 ` Kevin Rodgers
[not found] ` <mailman.6827.1158084485.9609.help-gnu-emacs@gnu.org>
2006-09-12 18:29 ` Floyd L. Davidson
2006-09-09 15:01 Bill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87irjton8r.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).