unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: set-transient-map and a question
Date: Wed, 12 Jul 2023 04:32:11 +0200	[thread overview]
Message-ID: <87ttu997x0.fsf@web.de> (raw)
In-Reply-To: p91wmz57uxa.fsf@google.com

"T.V Raman" <raman@google.com> writes:

> From my experimentation, it appeared (needs confirmation) that if
> kee-pressed was nil, the exit-func never got called

The code says that EXIT-FUN is always called.  Here is a simple test
case:

(set-transient-map emacs-lisp-mode-map nil
  (lambda () (message "!!!")))

Works as expected here: after hitting a random key I get the expected
`message'

> -- even though the function called itself recursively -- ie if
> keep-pressed is nil, and it calls itself, the behavior is
> indistinguishable from keep-pressed = t.

Note that nested transient maps are handled specially: the first (or
"outer") ones wait until the newest one is gone.  Maybe you hit that
case.

Michael.




  reply	other threads:[~2023-07-12  2:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  1:12 set-transient-map and a question T.V Raman
2023-07-11  8:03 ` Robert Pluim
2023-07-11 14:09   ` T.V Raman
2023-07-11 16:08     ` Robert Pluim
2023-07-11 17:16       ` T.V Raman
2023-07-11 17:44         ` Robert Pluim
2023-07-11 17:53           ` T.V Raman
2023-07-11 18:10             ` Bob Rogers
2023-07-11 20:29               ` Robert Pluim
2023-07-11 20:53                 ` T.V Raman
2023-07-12  8:51                   ` Robert Pluim
2023-07-12 13:49                     ` T.V Raman
2023-07-12  1:28                 ` Michael Heerdegen
2023-07-12  1:58                   ` T.V Raman
2023-07-12  2:32                     ` Michael Heerdegen [this message]
2023-07-12  2:49                       ` Michael Heerdegen
2023-07-12  3:21                         ` T.V Raman
2023-07-12  3:39                           ` Michael Heerdegen
2023-07-12  8:55                             ` Robert Pluim

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=87ttu997x0.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-devel@gnu.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).