From: Jared Finder via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Additional cleanup around xterm-mouse
Date: Sun, 22 Nov 2020 15:56:50 -0800 [thread overview]
Message-ID: <3e3933d8ec1d5d3f6809385a8ac5f447@finder.org> (raw)
In-Reply-To: <838savys2v.fsf@gnu.org>
On 2020-11-21 1:31 am, Eli Zaretskii wrote:
>> Date: Thu, 19 Nov 2020 00:03:30 -0800
>> From: Jared Finder <jared@finder.org>
>> Cc: emacs-devel@gnu.org
>>
>> > I don't think I follow. All the places where you need changes are
>> > related to handling mouse events, so why cannot it be specific to
>> > xt-mouse?
>>
>> There is a bug in widget-key-sequence-read-event's usage of keyboard
>> events specifically.
>>
>> The function widget-key-sequence-read-event currently does not
>> correctly
>> translate function keys for the terminal. It has code that attempts
>> to
>> apply function-key-map, but does not apply input-decode-map, so it can
>> not read function keys. (Additionally, it should be using
>> local-function-key-map now.)
>
> OK, but that means widget-key-sequence-read-event has a bug that needs
> to be fixed regardless.
>
> So I'm still asking why can't we do something like
>
> (if xterm-mouse-mode
> (read-key)
> (read-event))
>
> in all the affected places that currently call read-event?
This can be done in all places except widget-key-sequence-read-event
(see below for an explanation). Though it feels like a bad solution as
the info pages clearly state right now that if you want to read
translated events, you should use read-key, not read-event. Mouse
events always could be translated because of xterm-mouse-mode, so isn't
this just a bug?
I completely agree with the goal to make sure to preserve backward
compatibility issues, but I think a better approach would be to add the
additional functionality to read-key to make it a safe replacement for
read-event. (This seems aligned with how I read Stefan's recent comment
on this thread as well.)
By the way, the info text I'm referring to is the following excerpt from
(elisp)Top > Command Loop > Reading Input > Reading One Event.
We emphasize that, unlike ‘read-key-sequence’, the functions
‘read-event’, ‘read-char’, and ‘read-char-exclusive’ do not perform the
translations described in Translation Keymaps. If you wish to
read a single key taking these translations into account, use the
function ‘read-key’:
> So I'm still wary of making such a
> significant change, even though we are talking about a small number of
> relatively minor feature (with the sole exception of Ediff, perhaps).
Note: the wid-edit.el change is also pretty major and where I first
noticed this. Without some fix there, interaction with widgets in
Customize buffers with an xterm mouse will cause infinite loops that
only C-g can escape.
>> (let ((ev2 (and (memq 'down (event-modifiers ev))
>> - (read-event)))
>> - (tr (and (keymapp function-key-map)
>> - (lookup-key function-key-map (vector ev)))))
>> + (read-key)))
>> + ;; This is actually a separate bug-fix. `function-key-map'
>> + ;; does not contain any term-specific function key mappings
>> + ;; like f13 --> S-f1.
>> + (tr (and (keymapp local-function-key-map)
>> + (lookup-key local-function-key-map (vector ev)))))
>
> Let's fix this part separately.
The underlying issue with function keys is the same as the xterm-mouse
issue (failure to apply input-decode-map), so the solutions may be
intertwined. Terminal function keys and xterm mouse events both get
decoded through input-decode-map.
Note that because function keys are also affected, for this function the
check whether to use read-key or read-event would need to be something
like:
(if (eq window-system nil) ; This is correct on Linux and macOS, not
sure
; if accurate for other platforms
(read-key)
(read-event))
Without the change from read-event to read-key throughout this function,
'ev' will never contain an event that would be translated by
local-function-key-map or function-key-map from what I've seen. It may
be a better path to convert this function to just call (read-key
"Prompt" t) like the rest of the modifications. If this is done, then
local-function-key-map is already applied. I realize that is a behavior
change, but given how fragile reconstructing the way translation maps
already is, I think it is worth considering.
-- MJF
next prev parent reply other threads:[~2020-11-22 23:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 6:29 Additional cleanup around xterm-mouse Jared Finder via Emacs development discussions.
2020-11-16 17:30 ` Jared Finder via Emacs development discussions.
2020-11-18 17:40 ` Eli Zaretskii
2020-11-19 8:03 ` Jared Finder via Emacs development discussions.
2020-11-21 9:31 ` Eli Zaretskii
2020-11-22 23:56 ` Jared Finder via Emacs development discussions. [this message]
2020-11-28 16:36 ` Eli Zaretskii
2020-12-01 7:36 ` Jared Finder via Emacs development discussions.
2020-12-01 15:21 ` Stefan Monnier
2020-12-01 18:23 ` Eli Zaretskii
2020-12-02 6:45 ` Jared Finder via Emacs development discussions.
2020-12-02 16:53 ` Stefan Monnier
2020-12-03 5:46 ` Jared Finder via Emacs development discussions.
2020-12-03 14:45 ` Stefan Monnier
2020-12-03 17:31 ` Jared Finder via Emacs development discussions.
2020-12-14 0:54 ` Jared Finder via Emacs development discussions.
2020-12-14 15:32 ` Eli Zaretskii
2020-12-16 5:30 ` Jared Finder via Emacs development discussions.
2020-12-19 18:32 ` Eli Zaretskii
2020-12-19 22:50 ` Stefan Monnier
2020-12-20 7:26 ` Jared Finder via Emacs development discussions.
2020-12-20 14:07 ` Stefan Monnier
2020-12-20 23:27 ` Jared Finder via Emacs development discussions.
2020-12-23 16:52 ` Eli Zaretskii
2020-12-23 17:21 ` Jared Finder via Emacs development discussions.
2020-12-24 18:43 ` Eli Zaretskii
2020-12-14 0:36 ` Jared Finder via Emacs development discussions.
2020-11-21 17:00 ` Stefan Monnier
2020-11-21 8:23 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2020-12-26 23:49 Jared Finder via Emacs development discussions.
2020-12-27 15:36 ` Stefan Monnier
2020-12-27 16:30 ` Jared Finder via Emacs development discussions.
2020-12-27 17:10 ` Stefan Monnier
2020-12-28 0:22 ` Jared Finder via Emacs development discussions.
2021-01-02 8:17 ` Eli Zaretskii
2021-01-02 22:20 ` Jared Finder via Emacs development discussions.
2021-01-09 12:27 ` Eli Zaretskii
2021-01-09 23:01 ` Jared Finder via Emacs development discussions.
2021-01-15 11:54 ` Eli Zaretskii
2020-11-15 8:49 Jared Finder via Emacs development discussions.
2020-11-15 18:11 ` Eli Zaretskii
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=3e3933d8ec1d5d3f6809385a8ac5f447@finder.org \
--to=emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=jared@finder.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).