From: Peter Dyballa <Peter_Dyballa@web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Location of .emacs file under `su` and `su -`?
Date: Tue, 22 Aug 2006 18:08:28 +0200 [thread overview]
Message-ID: <048DDA5E-3A9E-44D5-94EA-C0CA1342199C@web.DE> (raw)
In-Reply-To: <386rr3-n6k.ln1@news.ducksburg.com>
Am 22.08.2006 um 13:26 schrieb Adam Funk:
> When emacs starts up, does it actually look up "~${LOGNAME}/.emacs"
> instead of (what I would expect) "${HOME}/.emacs"?
You might be able to avoid asking this question by invoking GNU Emacs
with the option --user or -u and then passing that user's login name.
Could be $USER is sufficient ...
--
Greetings
Pete
“Computers are good at following instructions, but not at reading
your mind.”
- D. E. Knuth, The TeXbook, Addison-Wesley 1984, 1986, 1996, p. 9
next prev parent reply other threads:[~2006-08-22 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 11:26 Location of .emacs file under `su` and `su -`? Adam Funk
2006-08-22 16:08 ` Peter Dyballa [this message]
[not found] ` <mailman.5450.1156262916.9609.help-gnu-emacs@gnu.org>
2006-08-23 10:15 ` Adam Funk
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=048DDA5E-3A9E-44D5-94EA-C0CA1342199C@web.DE \
--to=peter_dyballa@web.de \
--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).