From: Jean Louis <bugs@gnu.support>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60645@debbugs.gnu.org
Subject: bug#60645: 30.0.50; interactive MODES not detected properly
Date: Sun, 8 Jan 2023 14:26:18 +0300 [thread overview]
Message-ID: <Y7qoWsydife+/5Da@protected.localdomain> (raw)
In-Reply-To: <83fsclqtdt.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2023-01-08 12:15]:
> Maybe one of the inconsistencies is your expectations. What did you
> expect to happen in each case, and why?
For this function:
(defun my-function ()
(interactive nil '(text-mode mail-mode))
(message "Hello"))
> If MODES is present, it should be a list of mode names (symbols) that
> this command is applicable for. The main effect of this is that
> ‘M-x TAB’ (by default) won’t list this command if the current buffer’s
> mode doesn’t match the list. That is, if either the major mode isn’t
> derived from them, or (when it’s a minor mode) the mode isn’t in effect.
I expect that M-x TAB shows it in this mail-mode, but it does not show
it this time. That is one of expectations, among several.
In general, I would like to setup functions NOT to show in modes where
they should not be shown.
I feel this function does not work.
If you have working example, show me.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-01-08 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 6:19 bug#60645: 30.0.50; interactive MODES not detected properly Jean Louis
[not found] ` <handler.60645.B.167315884819377.ack@debbugs.gnu.org>
2023-01-08 6:33 ` bug#60645: Acknowledgement (30.0.50; interactive MODES not detected properly) Jean Louis
2023-01-08 9:15 ` bug#60645: 30.0.50; interactive MODES not detected properly Eli Zaretskii
2023-01-08 11:26 ` Jean Louis [this message]
2023-01-08 12:11 ` Eli Zaretskii
2023-01-08 21:39 ` Jean Louis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y7qoWsydife+/5Da@protected.localdomain \
--to=bugs@gnu.support \
--cc=60645@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.