GNU bug report logs - #16150
Emacs not deleting lock files when system-name is set to nil

Previous Next

Full log

View this message in rfc822 format

From: Micky <mickylmartin <at> gmail.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 16150 <at> debbugs.gnu.org
Subject: bug#16150: Emacs not deleting lock files when system-name is set to nil
Date: Sun, 15 Dec 2013 01:25:52 +0500

[Message part 1 (text/plain, inline)]

Ehh.. just because one could do that? And setting it to nil shoots no
errors during the --init. This gives enough assumptions, I believe ;)


On Sun, Dec 15, 2013 at 1:22 AM, Glenn Morris <rgm <at> gnu.org> wrote:

> Micky wrote:
>
> > When setting system-name to nil (should that be allowed?), Emacs forgets
> > how to delete the lock files '.#.*' and all subsequent startups complain
> > about lockups by old dead PIDs.
>
> I think this is a "don't do that, then".
> If Emacs fails to set system-name, that is a bug.
> If you actively set system-name to nil, that's just shooting yourself
> in the foot.
> Why did you want to do that, and what made you think it would work?
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.