From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alex <agrambot@gmail.com>
Cc: Olaf Rogalsky <olaf.rogalsky@t-online.de>, 29150@debbugs.gnu.org
Subject: bug#29150: Fwd: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode)
Date: Thu, 09 Nov 2017 03:21:47 -0500 [thread overview]
Message-ID: <jwvy3nfx40k.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <871sl8j7bv.fsf@gmail.com> (Alex's message of "Thu, 09 Nov 2017 00:26:44 -0600")
>> I'm not sure why, or what it would say. `read-key` is a reasonably good
>> replacement for `read-event`, but it's still pretty brittle.
>> The better solution is to not "read" anything and let the main loop do
>> it for you (which is why I changed mouse-drag-track to use
>> set-transient-map instead of mucking with `read-event` or `read-key`).
> Assuming that no one ports evil-mode's code or updates the code in
> `mouse-drag-secondary' (there's already a FIXME for this there), is
> using `read-key' inside of `track-mouse' an acceptable stopgap solution?
I'm not sure I understand the question, but I think so, yes.
> Is it brittle enough to not apply the change to emacs-26?
I think in the help.el case, it would be a clear improvement.
Stefan
next prev parent reply other threads:[~2017-11-09 8:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 17:39 bug#29159: 27.0.50; Hang in HTML/CSS code Lars Ingebrigtsen
2017-11-05 19:53 ` bug#29159: 26.0.90; Input decoding is sometimes skipped in TTY (xterm-mouse-mode) Olaf Rogalsky
2017-11-05 7:42 ` bug#29150: " Alex
2017-11-05 20:34 ` bug#29150: Fwd: " Olaf Rogalsky
2017-11-06 15:59 ` Eli Zaretskii
2017-11-06 21:43 ` Olaf Rogalsky
2017-11-11 9:15 ` Eli Zaretskii
2017-11-12 8:25 ` Alex
2017-11-12 11:17 ` Eli Zaretskii
2017-11-13 0:00 ` Alex
2017-11-13 15:51 ` Eli Zaretskii
2017-11-13 18:14 ` Olaf Rogalsky
2017-11-13 18:31 ` Eli Zaretskii
2017-11-13 19:09 ` Olaf Rogalsky
2017-11-12 16:30 ` Stefan Monnier
2020-08-10 16:25 ` Stefan Kangas
2021-05-10 12:14 ` bug#29150: " Lars Ingebrigtsen
2017-11-08 20:57 ` bug#29150: Fwd: " Alex
2017-11-08 21:30 ` Alex
2017-11-08 22:13 ` Stefan Monnier
2017-11-09 6:26 ` Alex
2017-11-09 8:21 ` Stefan Monnier [this message]
2017-11-09 15:47 ` Eli Zaretskii
2017-11-05 21:55 ` bug#29159: 27.0.50; Hang in HTML/CSS code Simen Heggestøyl
2017-11-12 18:50 ` Tom Tromey
2017-11-26 2:17 ` Stefan Monnier
2017-11-26 14:52 ` Simen Heggestøyl
2017-11-26 17:36 ` Tom Tromey
2017-11-25 20:49 ` bug#29159: done Tom Tromey
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=jwvy3nfx40k.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=29150@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=olaf.rogalsky@t-online.de \
/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).