From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Emacs - xemacs question
Date: Sat, 23 Nov 2002 22:08:29 +0100 [thread overview]
Message-ID: <84hee8at9u.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: mailman.1037870783.12561.help-gnu-emacs@gnu.org
Urban Gabor <gabaux@freemail.hu> writes:
> The emacs works properly as I have set in the config file
> (line-number mode, K&R style in C/C++ mode, etc). Though
> Xemacs uses the same settings, it is not working the same.
Recent versions of XEmacs read ~/.xemacs/init.el (and some other
files) if it exists, instead of ~/.emacs. Does this help?
I'm fishing in the dark. If this does not help, please provide more
data, such as Emacs and XEmacs versions, CC mode versions in both
cases, contents of ~/.emacs and of other init files, description of
the different behavior.
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next parent reply other threads:[~2002-11-23 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1037870783.12561.help-gnu-emacs@gnu.org>
2002-11-23 21:08 ` Kai Großjohann [this message]
2002-11-21 9:25 Emacs - xemacs question Urban Gabor
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=84hee8at9u.fsf@lucy.cs.uni-dortmund.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).