From: kj <socyl@987jk.com.invalid>
To: help-gnu-emacs@gnu.org
Subject: Inexplicable flaw: non-overridable .emacs
Date: Thu, 15 Mar 2007 18:15:15 +0000 (UTC) [thread overview]
Message-ID: <etc2fj$7dl$1@reader2.panix.com> (raw)
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.
If this is correct, I seems to me an inexplicable design flaw. Is
there some fundamental reason for it?
Of course, if my understanding is incorrect, please toss me a
cluebrick!
TIA!
kj
--
NOTE: In my address everything before the first period is backwards;
and the last period, and everything after it, should be discarded.
next reply other threads:[~2007-03-15 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 18:15 kj [this message]
2007-03-15 18:24 ` Inexplicable flaw: non-overridable .emacs David Kastrup
2007-03-15 19:08 ` Maarten Bergvelt
2007-03-15 20:14 ` Eli Zaretskii
[not found] ` <mailman.972.1173989687.7795.help-gnu-emacs@gnu.org>
2007-03-17 13:43 ` kj
2007-03-17 13:54 ` Joost Kremers
2007-03-17 15:11 ` Kevin Rodgers
2007-03-17 15:43 ` David Hansen
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='etc2fj$7dl$1@reader2.panix.com' \
--to=socyl@987jk.com.invalid \
--cc=help-gnu-emacs@gnu.org \
/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).