From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: emacs just won't let go of the past - old settings
Date: Wed, 26 Feb 2003 10:14:46 +0100 [thread overview]
Message-ID: <84lm03v1x5.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: BNP6a.4393$EN3.34673@newsfep4-glfd.server.ntli.net
"chris.danx" <spamoff.danx@ntlworld.com> writes:
> Can anyone help with this? I have been trying to track down a problem
> with font-lock-mode not highlighting new buffers, but have ran into
> another problem. To isolate the error, .emacs was renamed to
> something else and emacs was started. However emacs has remembered
> some settings that where set via a menu added from code .emacs.
Strange. Maybe your site admin has changed things so that
custom-file is changed and the new file is loaded? Type C-h v
custom-file RET to find out.
--
A preposition is not a good thing to end a sentence with.
next prev parent reply other threads:[~2003-02-26 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 19:49 emacs just won't let go of the past - old settings chris.danx
2003-02-26 9:14 ` Kai Großjohann [this message]
2003-02-26 18:25 ` chris.danx
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=84lm03v1x5.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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).