From: Eli Zaretskii <eliz@gnu.org>
To: monnier@iro.umontreal.ca, Psionic K <psionik@positron.solutions>
Cc: 74936@debbugs.gnu.org
Subject: bug#74936: 30.0.91; special-event-map does not respect t
Date: Sat, 04 Jan 2025 13:35:06 +0200 [thread overview]
Message-ID: <86r05ierrp.fsf@gnu.org> (raw)
In-Reply-To: <CADQMGASfEAmE+r0k3yB2mMB5L7CMWK1JC8pPQmFDZwUfn9_p=g@mail.gmail.com> (message from Psionic K on Thu, 19 Dec 2024 20:54:56 +0900)
Ping! Stefan, any suggestions?
> From: Psionic K <psionik@positron.solutions>
> Date: Thu, 19 Dec 2024 20:54:56 +0900
> Cc: Eli Zaretskii <eliz@gnu.org>, Psionic K <psionik@positron.solutions>, 74936@debbugs.gnu.org
>
> I'll try the patch tomorrow.
>
> > could be satisfied in many other ways
>
> Since I have code that will need to work on Emacs 30-ish, I have to
> ask if any of the other ways are good ways?
>
> In the meantime I've thought of using `overriding-terminal-local-map'
> with a keyhole nil binding for only my expected input in between
> idling. A "keyhole" map that allows 'e' through.
>
> (let ((km (list 'keymap (cons t #'pmx--haha))))
> (keymap-set km "M-x" #'counsel-M-x)
> (keymap-set km "e" nil)
> (use-local-map km))
>
> (current-local-map)
>
> To completely prevent fat-fingers, I then need to close the keyhole
> after each first pass. Then there's the problem of input calling
> commands that clobber `overriding-terminal-local-map'.
>
> In conclusion, the special map feels like the only correct one to
> express the idea.
>
next prev parent reply other threads:[~2025-01-04 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 6:41 bug#74936: 30.0.91; special-event-map does not respect t Psionic K
2024-12-18 13:57 ` Eli Zaretskii
2024-12-18 23:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-19 11:54 ` Psionic K
2025-01-04 11:35 ` Eli Zaretskii [this message]
2025-01-04 21:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-04 22:16 ` Psionic K
2025-01-04 22:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-05 7: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=86r05ierrp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74936@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=psionik@positron.solutions \
/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).