Re: error in server-running-p on M$

["Juanma Barranquero" <lekktu@gmail.com>]

On Sun, Nov 23, 2008 at 06:21, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> To avoid clobbering 1's auth file.

Then, it is not really necessary to connect with 1's server. Just the
fact that there's a local Emacs with the same PID that the one saved
in the authentication file, and acting as a local server, should be
reason enough for 2 to refuse overwriting the auth file.

> Assuming that server-start is changed to signal an error if
> server-running-p returns non-nil, could you show us again the scenario
> where the auth file is clobbered and in what way it's clobbered?

No, I've never claimed that. If server-start signals an error when
`server-running-p' returns non-nil, the auth file won't be clobbered.
(At least, in normal configurations; I'm not sure that is impossible
for some combination of non local servers, remote home user
directories, etc. That's left as an exercise for the people who
usually works in such environments ;-)

But we're trying to fix the easy, common problem first, aren't we?

             Juanma