From: "T.V Raman" <raman@google.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: set-transient-map and a question
Date: Tue, 11 Jul 2023 20:21:27 -0700 [thread overview]
Message-ID: <p91sf9terwo.fsf@google.com> (raw)
In-Reply-To: <87o7kh9741.fsf@web.de> (Michael Heerdegen's message of "Wed, 12 Jul 2023 04:49:34 +0200")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 786 bytes --]
Michael Heerdegen <michael_heerdegen@web.de> writes:
For me, hitting c-x c-e at the end of that code while in the gnus
article buffer did not appear to work, it continued to call keys in the
buffer-local gnus article mode.
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> 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.
>
> Note that this doesn't happen for `eq' maps. But if your recursive
> calls install a new transient map that is only `equal' to the first one
> it's treated as an additional transient map hiding the old one.
>
> Michael.
>
>
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1 0Ü8
next prev parent reply other threads:[~2023-07-12 3:21 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
2023-07-12 2:49 ` Michael Heerdegen
2023-07-12 3:21 ` T.V Raman [this message]
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=p91sf9terwo.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.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).