GNU bug report logs - #17170
24.3.50; debug: Terminal 3 is locked, cannot read from it

Previous Next

Full log

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

From: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 17170 <at> debbugs.gnu.org
Subject: Re: bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read
 from it
Date: Fri, 20 Mar 2015 17:55:20 +0100

Le 20/03/2015 17:42, Eli Zaretskii a écrit :
>> Date: Fri, 20 Mar 2015 16:47:50 +0100
>> From: Nicolas Richard <theonewiththeevillook <at> yahoo.fr>
>> CC: 17170 <at> debbugs.gnu.org
>> 
>> I'll appreciate any help. I guess I should somehow detect when/why emacs tries to access that initial frame, F1, but where would I hook ?
> 
> Hard to tell.  Can you be more specific about "access that frame"?
> What kind of access are we talking about?

IMO that frame should not ever be used for displaying a buffer, so if emacs ever tries to do that, I want to know why it does it.

> What happens if you delete that frame?

I did (delete-frame (cadr (frame-list))), and now I can't delete my GUI frame anymore : if I do "C-x C-c", emacs asks me if I want to exit emacs. If I do C-x 5 0, I get:
Debugger entered--Lisp error: (error "Attempt to delete the sole visible or iconified frame")

Nicolas.

Previous Next

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