From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org, snogglethorpe@gmail.com,
michael.cadilhac@lrde.org, rms@gnu.org, miles@gnu.org
Subject: Re: Use .emacs.d in savehist.el
Date: Tue, 01 Nov 2005 07:54:57 -0500 [thread overview]
Message-ID: <87k6fsfrz2.fsf@stupidchicken.com> (raw)
In-Reply-To: <87vezd0xa4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 01 Nov 2005 00:12:45 -0500")
>> I looked into the possibility of making Miles' "find customization
>> file" function do a chown and chgrp on the customization file, so that
>> this problem won't arise. But Emacs doesn't have any built-in chown
>> or chgrp. Dired can do it, but it's by calling an external program.
>
> I tend to think that people who use "emacs -u foo" as root just get what
> they deserve.
In that case, maybe using root's own .emacs.d is actually the safer
thing to do, even if it is inconsistent with the meaning of "-u foo".
Here are two possibilities I can think of:
1. Let `init-file-user' apply to the init file only. The init file
has enough complications anyway that Miles' proposed function won't
do the trick (apart from `init-file-user', there is the MS-DOS
"_emacs" issue). That function can be implemented so other
libraries can use it, but it ignores init-file-user.
2. Go through the code in such a way that when init-file-user is
non-nil, files are *read* from ~INIT_FILE_USER/.emacs.d, but
*written* to the user's own home directory. This can be made
simpler by implementing Miles' function with an optional
`read-only' argument, but we will still have to go through all the
places that currently use .emacs.d to make sure they DTRT.
Personally, I like the first possibility because it's much
simpler... no one has actually complained about the interaction
between .emacs.d and init-file-user (at least until I brought it up
:-P), so I think it's not a big enough problem to justify a
far-reaching fix, especially close to release.
next prev parent reply other threads:[~2005-11-01 12:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 15:58 Use .emacs.d in savehist.el Stefan Monnier
2005-10-24 21:22 ` Kim F. Storm
2005-10-25 20:27 ` Richard M. Stallman
2005-10-25 9:30 ` Hrvoje Niksic
2005-10-25 14:30 ` David Kastrup
2005-10-25 14:51 ` Stefan Monnier
2005-10-25 19:13 ` Hrvoje Niksic
[not found] ` <87oe5e977f.fsf@mahaena.lrde>
2005-10-25 9:59 ` Michael Cadilhac
2005-10-25 14:54 ` Stefan Monnier
2005-10-26 16:46 ` Richard M. Stallman
2005-10-26 23:28 ` Miles Bader
2005-10-27 3:58 ` Richard M. Stallman
2005-10-27 16:53 ` Kevin Rodgers
2005-10-28 16:19 ` Richard M. Stallman
2005-10-28 20:16 ` Miles Bader
2005-10-29 5:12 ` Richard M. Stallman
2005-10-29 17:31 ` Kim F. Storm
2005-10-30 0:03 ` Miles Bader
2005-10-29 3:51 ` Chong Yidong
2005-10-29 20:33 ` Richard M. Stallman
2005-10-30 4:00 ` Chong Yidong
2005-10-30 4:30 ` Miles Bader
2005-10-30 13:59 ` Chong Yidong
2005-10-31 1:14 ` Richard M. Stallman
2005-10-31 2:29 ` Chong Yidong
2005-11-01 2:14 ` Richard M. Stallman
2005-11-01 3:43 ` Chong Yidong
2005-11-01 5:12 ` Stefan Monnier
2005-11-01 12:54 ` Chong Yidong [this message]
2005-11-02 10:27 ` Richard M. Stallman
2005-11-02 15:54 ` Stefan Monnier
2005-11-02 10:26 ` Richard M. Stallman
2005-11-02 10:26 ` Richard M. Stallman
2005-10-27 9:16 ` Kim F. Storm
2005-10-30 4:07 ` Chong Yidong
2005-10-25 15:58 ` Richard M. Stallman
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=87k6fsfrz2.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=michael.cadilhac@lrde.org \
--cc=miles@gnu.org \
--cc=rms@gnu.org \
--cc=snogglethorpe@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).