From: Ken Raeburn <raeburn@permabit.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21473@debbugs.gnu.org
Subject: bug#21473: 24.5; very slow tooltip display to sort-of-slow remote display
Date: Thu, 01 Oct 2015 12:51:14 -0400 [thread overview]
Message-ID: <6e4mia3531.fsf@just-testing.permabit.com> (raw)
In-Reply-To: <6ebnci3o1s.fsf@just-testing.permabit.com> (Ken Raeburn's message of "Thu, 01 Oct 2015 06:01:35 -0400")
Ken Raeburn <raeburn@permabit.com> writes:
> It occurs to me that maybe we can get rid of the XSync in
> x_catch_errors, if we record in the x_error_message_stack structure the
> serial number for the first request for which errors should be recorded
> there, using XNextRequest. If the error handler sees an older serial
> number in the error-event structure, then it looks at the next entry in
> the stack and tries again. Something similar may work for
> x_uncatch_errors too.
Ah...can the stacked entries refer to different displays?
That would make things more complicated.
next prev parent reply other threads:[~2015-10-01 16:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 8:13 bug#21473: 24.5; very slow tooltip display to sort-of-slow remote display Ken Raeburn
2015-09-15 14:32 ` Eli Zaretskii
2015-09-15 22:03 ` Ken Raeburn
2015-09-26 7:03 ` Eli Zaretskii
2015-09-27 10:35 ` Ken Raeburn
2015-09-27 10:38 ` Eli Zaretskii
2015-09-27 13:29 ` Ken Raeburn
2015-09-29 20:15 ` Ken Raeburn
2015-09-30 7:23 ` Eli Zaretskii
2015-10-01 10:01 ` Ken Raeburn
2015-10-01 16:51 ` Ken Raeburn [this message]
2015-10-04 9:45 ` Eli Zaretskii
2015-10-04 18:02 ` Ken Raeburn
2015-10-04 19:40 ` Eli Zaretskii
2015-10-05 5:38 ` Ken Raeburn
2015-10-05 6:25 ` Eli Zaretskii
2015-10-06 2:15 ` Ken Raeburn
2015-10-06 2:44 ` Eli Zaretskii
2015-10-06 9:30 ` Ken Raeburn
2015-10-06 14:46 ` Eli Zaretskii
2015-10-07 6:09 ` Ken Raeburn
2015-10-07 15:31 ` Eli Zaretskii
2015-10-08 6:04 ` Ken Raeburn
2015-10-08 8:12 ` Ken Raeburn
2021-09-19 22:29 ` Stefan Kangas
2022-04-24 13:19 ` Lars Ingebrigtsen
2022-04-25 2:09 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 8:02 ` Lars Ingebrigtsen
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=6e4mia3531.fsf@just-testing.permabit.com \
--to=raeburn@permabit.com \
--cc=21473@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).