From: Sean McLaughlin <seanmcl@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Peter Szilagyi <pszilagyi@janestreet.com>, 13655@debbugs.gnu.org
Subject: bug#13655: 23.2; sit-for doesn't return on input in other X displays
Date: Fri, 22 Feb 2013 13:08:06 -0500 [thread overview]
Message-ID: <CAO4dZbfvfV6WBMWuEuEHnfbMiE5Aq1Ahr7DwYa+_dG4rs6MvJg@mail.gmail.com> (raw)
In-Reply-To: <jwv7gm1152a.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
I confirm that commenting the line
// temporarily_switch_to_single_kboard (NULL);
solves the problem. Are there a battery of tests we can run with this
change so we can
make sure we didn't hose Emacs in some other way?
On Thu, Feb 21, 2013 at 9:05 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> > That is about all I know. Just not calling
> > temporarily_switch_to_single_kboard may solve this, but may have other
> > side effects.
>
> IIUC the temporarily_switch_to_single_kboard is there so that when you
> use Emacs on several terminals at the same time, interleaved events from
> the various terminals is "properly" de-interleaved.
> The intended use case is "several terminals on several machines with
> different people on each machine".
>
> I think a more important use case is "press <key1> on terminal1 and
> <key2> on terminal2 almost at the same time and <key1> and <key2> both
> expand to escape byte sequences". So it's important that the bytes from
> each terminal don't get mixed up, otherwise input-decode-map won't be
> able to turn them back into <key1> and <key2>. IIUC this use case does
> not require temporarily_switch_to_single_kboard in call-interactively.
>
>
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 1802 bytes --]
prev parent reply other threads:[~2013-02-22 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 17:38 bug#13655: 23.2; sit-for doesn't return on input in other X displays Peter Szilagyi
2013-02-16 17:13 ` Jan Djärv
2013-02-20 16:42 ` Peter Szilagyi
2013-02-20 16:45 ` Sean McLaughlin
2013-02-21 18:29 ` Jan Djärv
2013-02-22 2:05 ` Stefan Monnier
2013-02-22 18:08 ` Sean McLaughlin [this message]
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=CAO4dZbfvfV6WBMWuEuEHnfbMiE5Aq1Ahr7DwYa+_dG4rs6MvJg@mail.gmail.com \
--to=seanmcl@gmail.com \
--cc=13655@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=pszilagyi@janestreet.com \
/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).