unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 45834@debbugs.gnu.org
Subject: bug#45834: 28.0.50; Mouse events in terminal emacs
Date: Wed, 08 Sep 2021 16:34:18 +0300	[thread overview]
Message-ID: <83mtonmbs5.fsf@gnu.org> (raw)
In-Reply-To: <83o893mc1g.fsf@gnu.org> (message from Eli Zaretskii on Wed, 08 Sep 2021 16:28:43 +0300)

> Date: Wed, 08 Sep 2021 16:28:43 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 45834@debbugs.gnu.org
> 
> > No, `C-h k' waits for the next real input event.
> 
> Which is the focus-in event, right?  Or what do you mean by "real
> input event"?

Actually, there could be one more way for us to get that weird echo:
if Emacs thought that "ESC [ I" was a prefix key.  See that dash after
the sequence? that's what Emacs displays after key-echo when it
received a partial sequence, like if you type "C-x" and wait.  So
perhaps somehow Emacs thinks these focus-in events are prefix,
i.e. incomplete key sequence.






  parent reply	other threads:[~2021-09-08 13:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 23:29 bug#45834: 28.0.50; Mouse events in terminal emacs Brady
2021-01-19  6:38 ` Lars Ingebrigtsen
2021-01-19  8:24   ` Eli Zaretskii
2021-01-19 15:22     ` Lars Ingebrigtsen
2021-01-19 15:38       ` Eli Zaretskii
2021-01-19 15:41         ` Lars Ingebrigtsen
2021-09-08  9:34           ` Lars Ingebrigtsen
2021-09-08  9:51             ` Eli Zaretskii
2021-09-08  9:54               ` Lars Ingebrigtsen
2021-09-08 13:07                 ` Eli Zaretskii
2021-09-08 13:24                   ` Lars Ingebrigtsen
2021-09-08 13:28                     ` Eli Zaretskii
2021-09-08 13:32                       ` Lars Ingebrigtsen
2021-09-08 13:34                       ` Eli Zaretskii [this message]
2021-09-08 13:41                         ` Lars Ingebrigtsen
2021-09-08 13:52                           ` Eli Zaretskii
2021-09-08 14:22                             ` Lars Ingebrigtsen
2021-09-08 15:49                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-08 16:04                               ` Eli Zaretskii
2021-09-09  2:22                                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09  6:30                                   ` Eli Zaretskii
2021-09-09 18:54                                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-09 14:34                                   ` Lars Ingebrigtsen
2021-09-09 18:56                                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-08 16:06                               ` 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=83mtonmbs5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45834@debbugs.gnu.org \
    --cc=larsi@gnus.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).