unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: schwab@linux-m68k.org, 35180@debbugs.gnu.org, hboetes@gmail.com
Subject: bug#35180: 27.0.50; emacs daemon and “package” often inserts [I when opening file
Date: Sat, 27 Apr 2019 16:50:47 +0300	[thread overview]
Message-ID: <83o94rv9oo.fsf@gnu.org> (raw)
In-Reply-To: <87lfzvy7xw.fsf@tcd.ie> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Sat, 27 Apr 2019 13:00:11 +0100
> Cc: 35180@debbugs.gnu.org, Han Boetes <hboetes@gmail.com>
> 
> On successful startup (where [I is not inserted), I am greeted by the
> "focus in" message.
> 
> On unsuccessful startup (where [I is inserted), the message never
> appears, but term/xterm and xterm are present in features.

By "race" do you mean that xterm writes from more than one thread to
the same descriptor, which is used by Emacs as keyboard input, and the
two inputs mix up into one large mess?  If not, who is racing whom
here?

> Could this race somehow be caused by the pdumper?

One way of finding out would be to build Emacs --with-dumping=unexec.
I'd be surprised if it turned out to be pdumper, but who knows?

Thanks.





  reply	other threads:[~2019-04-27 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 13:33 bug#35180: 27.0.50; emacs daemon and “package” often inserts [I when opening file Han Boetes
2019-04-27  9:26 ` Han Boetes
2019-04-27  9:52   ` Eli Zaretskii
2019-04-27 10:32   ` Andreas Schwab
2019-04-27 12:00     ` Basil L. Contovounesios
2019-04-27 13:50       ` Eli Zaretskii [this message]
2019-04-27 13:53         ` Eli Zaretskii
2019-04-27 14:14       ` Eli Zaretskii
2019-04-27 20:35         ` Han Boetes
2019-05-04 23:07           ` Han Boetes
2020-09-20 18:07       ` Lars Ingebrigtsen
     [not found]         ` <CAOzo9e4DC9oetmE=AY6CbZc49syb0t2-Ua4dHd4AMkDiij-tGQ@mail.gmail.com>
2020-09-22 14:07           ` Lars Ingebrigtsen
2019-10-04 19:59   ` Han Boetes
2019-12-18 19:31     ` Han Boetes

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=83o94rv9oo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35180@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=hboetes@gmail.com \
    --cc=schwab@linux-m68k.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).