From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nicolas Richard <theonewiththeevillook@yahoo.fr>, 17170@debbugs.gnu.org
Subject: bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it
Date: Fri, 20 Mar 2015 19:37:54 +0100 [thread overview]
Message-ID: <871tkjwm4d.fsf@yahoo.fr> (raw)
In-Reply-To: <83pp83v9w6.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Mar 2015 19:47:21 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
>> IMO that frame should not ever be used for displaying a buffer
>
> Why not? Isn't it just a regular frame?
No : I never see it. IIUC running "emacs --daemon" creates that frame
but it is never shown to me.
>> > 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")
>
> That's expected, but the question is does the problem go away?
The problem was already gone after changing debugger-previous-window.
--
Nicolas
next prev parent reply other threads:[~2015-03-20 18:37 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 11:03 bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it Nicolas Richard
2014-04-02 16:26 ` Eli Zaretskii
2014-04-02 17:57 ` Nicolas Richard
2014-04-02 20:22 ` Eli Zaretskii
2014-04-03 7:16 ` Nicolas Richard
2014-04-06 10:08 ` Nicolas Richard
2014-04-06 16:25 ` Eli Zaretskii
2014-04-06 16:41 ` Nicolas Richard
2014-04-06 17:00 ` Eli Zaretskii
2014-04-06 17:01 ` Eli Zaretskii
2014-05-07 11:07 ` Nicolas Richard
2014-05-07 15:17 ` Eli Zaretskii
2014-05-07 15:26 ` Nicolas Richard
2015-03-20 15:47 ` Nicolas Richard
2015-03-20 16:42 ` Eli Zaretskii
2015-03-20 16:55 ` Nicolas Richard
2015-03-20 17:47 ` Eli Zaretskii
2015-03-20 18:37 ` Nicolas Richard [this message]
2015-03-20 19:54 ` martin rudalics
2015-03-21 17:46 ` Nicolas Richard
2015-03-22 12:05 ` martin rudalics
2015-03-22 17:56 ` Nicolas Richard
2015-12-26 14:08 ` Lars Ingebrigtsen
2015-12-26 19:15 ` Nicolas Richard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tkjwm4d.fsf@yahoo.fr \
--to=theonewiththeevillook@yahoo.fr \
--cc=17170@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).