GNU bug report logs - #78583
31.0.50; emacs --fg-daemon not protecting frame F1

Previous Next

Package: emacs;

Reported by: Madhu <enometh <at> meer.net>

Date: Sun, 25 May 2025 05:43:02 UTC

Severity: normal

Found in version 31.0.50

Done: martin rudalics <rudalics <at> gmx.at>

Full log


Message #26 received at 78583 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Madhu <enometh <at> meer.net>
Cc: rudalics <at> gmx.at, 78583 <at> debbugs.gnu.org
Subject: Re: bug#78583: 31.0.50; emacs --fg-daemon not protecting frame F1
Date: Wed, 28 May 2025 18:50:30 +0300
> Date: Wed, 28 May 2025 20:33:02 +0530 (IST)
> Cc: eliz <at> gnu.org, 78583 <at> debbugs.gnu.org
> From: Madhu <enometh <at> meer.net>
> 
> *  martin rudalics <afdfc9ce-f4b4-42f2-bc27-a210d356a8f7 <at> gmx.at>
> Wrote on Wed, 28 May 2025 16:01:03 +0200
> 
> >> If this is not a regression, i.e. killing the initial frame in a
> >> daemon session was previously allowed, then I don't think we should
> >> signal an error.  We might ask for confirmation, but even then I'm not
> >> sure.  If someone wants to kill that frame, why should Emacs protest?
> >
> > Maybe Madhu can tell us.
> 
> Because if F1 is deleted emacs can no longer function as a daemon --
> it cannot be detached.  It now has to be attached to some termminal.
> One should assume that this is not what is required by the user who
> started emacs in daemon mode.  I believe this is a defect in the
> original implemenataion of daemonised emacs. --Madhu

I understand, but I don't see why this should be forbidden.




This bug report was last modified 7 days ago.

Previous Next


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