rogue option init-file-user

rogue option init-file-user

[Luc Teirlinck]

init-file-user is usually rogue:

  init-file-user: Hide Value Value Menu String: 
     State: CHANGED outside Customize; operating on it here may be unreliable.

Before worrying what to do about that, the first thing to decide is
whether this really should be defined with defcustom.  I believe that
it should be defined with defvar.  It seems to me that to change this
variable in a way that actually works, the user should use a command
line option such as -q or -u.  Setting or saving it through Custom
appears to make little sense.

Sincerely,

Luc.

Re: rogue option init-file-user

[Lennart Borgman]

Luc Teirlinck wrote:

>init-file-user is usually rogue:
>
>  init-file-user: Hide Value Value Menu String: 
>     State: CHANGED outside Customize; operating on it here may be unreliable.
>
>Before worrying what to do about that, the first thing to decide is
>whether this really should be defined with defcustom.  I believe that
>it should be defined with defvar.  It seems to me that to change this
>variable in a way that actually works, the user should use a command
>line option such as -q or -u.  Setting or saving it through Custom
>appears to make little sense.
>
>Sincerely,
>
>Luc.
>  
>
Beside the above problem the value on w32 seems strange. I get the value 
"" with CVS Emacs from 2006-01-06 after .emacs have been read.

Re: rogue option init-file-user

[Eli Zaretskii]

> Date: Sat, 07 Jan 2006 15:01:54 +0100
> From: Lennart Borgman <lennart.borgman.073@student.lu.se>
> Cc: emacs-devel@gnu.org
> 
> Beside the above problem the value on w32 seems strange. I get the value 
> "" with CVS Emacs from 2006-01-06 after .emacs have been read.

This isn't strange, this is exactly what should happen.  The doc
string of init-file-user says, among other things:

    Otherwise, the value may be the null string, meaning use the init file
    for the user that originally logged in, or it may be a
    string containing a user's name meaning use that person's init file.

    In either of the latter cases, `(concat "~" init-file-user "/")'
    evaluates to the name of the directory where the `.emacs' file was
    looked for.

With the possible exception of the term ``null string'' (which really
means an empty string), this describes what you see: since the .emacs
file used was from the user ``that originally logged in'', you get the
value of "", and (concat "~" init-file-user "/") will yield "~/", your
home directory.

I fixed the doc string to say "empty string", for more clarity.

Re: rogue option init-file-user

[Lennart Borgman]

Eli Zaretskii wrote:

>>Date: Sat, 07 Jan 2006 15:01:54 +0100
>>From: Lennart Borgman <lennart.borgman.073@student.lu.se>
>>Cc: emacs-devel@gnu.org
>>
>>Beside the above problem the value on w32 seems strange. I get the value 
>>"" with CVS Emacs from 2006-01-06 after .emacs have been read.
>>    
>>
>
>This isn't strange, this is exactly what should happen.  The doc
>string of init-file-user says, among other things:
>
>    Otherwise, the value may be the null string, meaning use the init file
>    for the user that originally logged in, or it may be a
>    string containing a user's name meaning use that person's init file.
>
>    In either of the latter cases, `(concat "~" init-file-user "/")'
>    evaluates to the name of the directory where the `.emacs' file was
>    looked for.
>
>With the possible exception of the term ``null string'' (which really
>means an empty string), this describes what you see: since the .emacs
>file used was from the user ``that originally logged in'', you get the
>value of "", and (concat "~" init-file-user "/") will yield "~/", your
>home directory.
>
>I fixed the doc string to say "empty string", for more clarity.
>  
>
Thanks, sorry, I believe I should have understood that.

Re: rogue option init-file-user

[Richard M. Stallman]

    With the possible exception of the term ``null string'' (which really
    means an empty string)

"Null string" is another name for "empty string",
but I don't mind if we use the latter.

Re: rogue option init-file-user

[Richard M. Stallman]

      It seems to me that to change this
    variable in a way that actually works, the user should use a command
    line option such as -q or -u.  Setting or saving it through Custom
    appears to make little sense.

What do others think?

Re: rogue option init-file-user

[David Kastrup]

"Richard M. Stallman" <rms@gnu.org> writes:

>       It seems to me that to change this
>     variable in a way that actually works, the user should use a command
>     line option such as -q or -u.  Setting or saving it through Custom
>     appears to make little sense.
>
> What do others think?

I think that in the long run, it should be possible to save
customizations in several different files.  When loading customization
files, some variable property would keep track where to save changes
for that variable.  This property would be set to user-init-file for
custom-file by default.

However, that's not something to think about before the release, I
guess.  Short of that, I'd take custom-file out of customize for now,
and just make it a defvar.

I don't think a separate command line option is necessary.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: rogue option init-file-user

[Luc Teirlinck]

I believe that there is some confusion here.  We already decided in an
earlier discussion what to do with custom-file (at least in as far
Emacs 22 is concerned.)  `user-init-file' is currently not
customizable (and probably should not be either).

The present discussion concerns `init-file-user'.  This is a (to me)
internal variable which determines which user's init file is read.
The current defcustom seems to invite the user to specify some value
in the custom-set-variables form in his init file.  But when and if
Emacs is actually going to read that customization, it has already
decided which user's init file to read.  So it has no effect.

The user should specify which init file to read using a command line
option, such as -q or -u.  After that, it is too late.

Sincerely,

Luc.

Re: rogue option init-file-user

[Luc Teirlinck]

David Kastrup wrote:

   I don't think a separate command line option is necessary.

There currently _are_ such command line options: -q, -Q and -u.
To me, their necessity would not seem to be in doubt.

But again, I believe that you are talking about the wrong variable.

Sincerely,

Luc.

Re: rogue option init-file-user

[David Kastrup]

Luc Teirlinck <teirllm@dms.auburn.edu> writes:

> David Kastrup wrote:
>
>    I don't think a separate command line option is necessary.
>
> There currently _are_ such command line options: -q, -Q and -u.
> To me, their necessity would not seem to be in doubt.
>
> But again, I believe that you are talking about the wrong variable.

Apparently.  Sorry for the confusion.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: rogue option init-file-user

[Luc Teirlinck]

   I don't think a separate command line option is necessary.

To completely avoid confusion:  I am _not_ asking for a new command
line option.  My argument is that the user should use one of the
_existing_ ones if he wants no init file to be read (-q or -Q) or
if he wants another user's init file to be read (-u).

Trying to do it in his custom-set-variables form is not going to work
anyway.  All it could possibly do is confuse Emacs.

Sincerely,

Luc.

Re: rogue option init-file-user

[Giorgos Keramidas]

On 2006-01-07 13:57, "Richard M. Stallman" <rms@gnu.org> wrote:
>     It seems to me that to change this variable in a way that actually
>     works, the user should use a command line option such as -q or -u.
>     Setting or saving it through Custom appears to make little sense.
>
> What do others think?

I agree it makes little sense.  In several systems I use 'task based'
accounts, i.e.:

    keramida@flame:/home/keramida$ ls -l /home
    total 18
    drwxrwxr-x   6 build     build     -  512 Jan  3 07:51 build
    drwxrwxr-x   7 root      cvs       -  512 Oct 23 05:34 cvs
    drwxr-xr-x  46 keramida  keramida  - 2560 Jan  8 01:19 keramida
    drwx------   8 root      wheel     - 2048 Nov  3 03:35 lost+found
    drwxr-xr-x  15 ncvs      ncvs      - 1024 Jan  6 22:04 ncvs
    drwxrwxr-x   2 root      svn       -  512 Oct 23 05:09 svn
    keramida@flame:/home/keramida$

Even in setups like this one, where I may find myself typing:

    keramida$ sudo -i -u ncvs
    ncvs$ emacs -u keramida

to share a common startup file, it makes little sense to customize the
init-file-user.  Let's say that I'm logged in as `ncvs' and I customize
`init-file-user' to "keramida".  Where will it be saved?  Saving it in
~keramida/.emacs may not be possible, because I don't have write
permissions when I'm logged in as `ncvs'.  Saving it to ~ncvs/.emacs
will probably fail to load the next time I start Emacs with -u keramida.

I don't see how making this customizable can work, so Luc is right IMHO.

Re: rogue option init-file-user

[Richard M. Stallman]

Luc, unless someone shows (within some days) a good reason to want to
customize init-file-user, please change it to a defvar.