bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Nicolas Richard
Subject: bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it
Date: Fri, 20 Mar 2015 17:55:20 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

Le 20/03/2015 17:42, Eli Zaretskii a écrit :
>> Date: Fri, 20 Mar 2015 16:47:50 +0100
>> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
>> CC: 17170@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.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]