no notification about -u failure

no notification about -u failure

[Dan Jacobson]

No message seen, not even in *Messages*, that -u wasn't being used right.
$ emacs -nw --no-site-file -u /
$ emacs -nw --no-site-file -q -u /
$ emacs -nw --no-site-file -q -u nurdsburg /
GNU Emacs 21.4.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2005-10-03 on trouble, modified by Debian
Copyright (C) 2001 Free Software Foundation, Inc.

Hmmm, "2001" too.

Re: no notification about -u failure

[Kevin Rodgers]

Dan Jacobson wrote:
> No message seen, not even in *Messages*, that -u wasn't being used right.
> $ emacs -nw --no-site-file -u /
> $ emacs -nw --no-site-file -q -u /
> $ emacs -nw --no-site-file -q -u nurdsburg /
> GNU Emacs 21.4.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
>  of 2005-10-03 on trouble, modified by Debian
> Copyright (C) 2001 Free Software Foundation, Inc.
> 
> Hmmm, "2001" too.

Don't you even read the followups to your own bug reports?

http://lists.gnu.org/archive/html/bug-gnu-emacs/2005-06/msg00214.html

-- 
Kevin Rodgers

Re: no notification about -u failure

[Richard M. Stallman]

    No message seen, not even in *Messages*, that -u wasn't being used right.
    $ emacs -nw --no-site-file -u /
    $ emacs -nw --no-site-file -q -u /
    $ emacs -nw --no-site-file -q -u nurdsburg /
    GNU Emacs 21.4.1 (i486-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
     of 2005-10-03 on trouble, modified by Debian
    Copyright (C) 2001 Free Software Foundation, Inc.

    Hmmm, "2001" too.

Most of this was fixed already in the current devel version.
I will fix the rest.

Re: no notification about -u failure

[Kevin Rodgers]

Richard M. Stallman wrote:
 >     No message seen, not even in *Messages*, that -u wasn't being 
used right.
 >     $ emacs -nw --no-site-file -u /
 >     $ emacs -nw --no-site-file -q -u /
 >     $ emacs -nw --no-site-file -q -u nurdsburg /
...
 > Most of this was fixed already in the current devel version.
 > I will fix the rest.

Ah, that bug wasn't squashed, because (file-directory-p (concat "~" "/"))
is true.

Should the test also simply check that (eq (string-to-char 
init-file-user) ?/)
is false, or are there other problematic user names?  Is "" legal?  What 
about
":" et al. on VMS?

,----[ C-h f file-name-directory RET ]
| file-name-directory is a built-in function.
| (file-name-directory FILENAME)
|
| Return the directory component in file name FILENAME.
| Return nil if FILENAME does not include a directory.
| Otherwise return a directory spec.
| Given a Unix syntax file name, returns a string ending in slash;
| on VMS, perhaps instead a string ending in `:', `]' or `>'.
`----

-- 
Kevin Rodgers