unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: 17170@debbugs.gnu.org
Subject: bug#17170: 24.3.50; debug: Terminal 3 is locked, cannot read from it
Date: Fri, 20 Mar 2015 18:42:36 +0200	[thread overview]
Message-ID: <83twxfvcw3.fsf@gnu.org> (raw)
In-Reply-To: <550C4126.1000008@yahoo.fr>

> 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?

What happens if you delete that frame?





  reply	other threads:[~2015-03-20 16:42 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 [this message]
2015-03-20 16:55                   ` Nicolas Richard
2015-03-20 17:47                     ` Eli Zaretskii
2015-03-20 18:37                       ` Nicolas Richard
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=83twxfvcw3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=17170@debbugs.gnu.org \
    --cc=theonewiththeevillook@yahoo.fr \
    /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).