From: Unknown <unknown@unknown.invalid>
Subject: Re: Not processing my .emacs file?
Date: Thu, 13 Mar 2003 03:35:29 GMT [thread overview]
Message-ID: <50Tba.107246$em1.102660@news04.bloor.is.net.cable.rogers.com> (raw)
In-Reply-To: roy-DA56A7.20244112032003@reader2.panix.com
Roy Smith wrote:
> I'm working with XEmacs 20.4 on a Solaris box. As far as I can tell,
> it's not reading my .emacs file. None of the customizations I have in
> there seem to be taking effect. I put in '(message "hello")', which it
> ignored. I even put in some deliberate syntax errors, to no effect.
>
> What might be keeping it from reading my .emacs file?
Could it be that XEmacs prefers ~/.xemacs/init.el over ~/.emacs if you have
both?
--
Le
P.S. followup to c.e.xemacs
next prev parent reply other threads:[~2003-03-13 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 1:24 Not processing my .emacs file? Roy Smith
2003-03-13 3:35 ` Unknown [this message]
2003-03-13 11:14 ` Kai Großjohann
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='50Tba.107246$em1.102660@news04.bloor.is.net.cable.rogers.com' \
--to=unknown@unknown.invalid \
/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).