unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 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: Mon, 13 Nov 2017 17:51:23 +0200	[thread overview]
Message-ID: <831sl2mb2c.fsf@gnu.org> (raw)
In-Reply-To: <878tfbdp3a.fsf@gmail.com> (message from Alex on Sun, 12 Nov 2017 18:00:57 -0600)

> From: Alex <agrambot@gmail.com>
> Cc: olaf.rogalsky@t-online.de,  29150@debbugs.gnu.org
> Date: Sun, 12 Nov 2017 18:00:57 -0600
> 
> >> Perhaps the patch should be replaced on the master branch with one that
> >> uses `read-key' in all cases?
> >
> > Why the rush?
> 
> I don't mean to rush anything, but I figured that I should mention it
> before I forget about it.

The thing is, I'm not yet sure read-key is TRT in this case.  We have
a lousy record in our changes of input processing code: almost every
change caused subtle bugs that took many moons to find and fix.  I
think we should recognize this vulnerability and behave more
cautiously.

> > If you want this on the release branch, it should be affect only
> > xt-mouse.  If you propose this for master, see above.
> 
> Do you mean that I shouldn't rush the `read-key' change for
> `mouse-drag-secondary' in master, either?

I'd like first to see how it fares on the release branch (and on
master), when it is limited to xt-mouse.

> Would applying the previous diff for master and the following for
> emacs-26 be acceptable?

Looks OK for the release branch (from which it will be merged to
master).  I'd prefer to wait with a more radical change even on
master.  Maybe put a FIXME comment there, to the effect that we should
try removing the condition at some point.

Thanks.





  reply	other threads:[~2017-11-13 15:51 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 [this message]
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
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=831sl2mb2c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).