From: mbork@mbork.pl
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How to get all commands defined in a specified file (or files)?
Date: Mon, 11 Nov 2024 22:58:04 +0100 [thread overview]
Message-ID: <87r07hwhzn.fsf@mbork.pl> (raw)
In-Reply-To: <86ttcdikwz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 11 Nov 2024 22:18:36 +0200")
On 2024-11-11, at 22:18, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: mbork@mbork.pl
>> Date: Mon, 11 Nov 2024 20:36:33 +0100
>>
>> Hi all,
>>
>> say that I'd like to define a `execute-extended-command' alternative
>> which would only allow to run commands defined in a specified file. How
>> can I get all such commands? I know about `symbol-file', but I don't
>> know how it works (and it's complicated enough that I'm not sure I want
>> to study it ATM;-) - I tried to instrument it for edebug, but a quick
>> run revealed only that it's pretty mysterious). I also looked at the
>> property plist of a function name and saw that the filename is not kept
>> there. Any hints?
>
> We have a facility to mark commands as relevant to a major mode or a
> list of major modes. If your file defines a major mode, you can use
> this for doing what you want. See the command
> execute-extended-command-for-buffer. A more general facility is the
> variable read-extended-command-predicate.
I know, it's cool, I even blogged about it!
(https://mbork.pl/2021-03-27_The_interactive_clause_and_modes).
But what I'm asking is something very different. I explicitly don't
want commands related to a certain mode (major or minor), but commands
defined in a specific file. I know that every function somehow "knows"
where its source is (because it's shown by `describe-function'), but I
want to be able to get that info (for ex., in a function I'd put in
`read-extended-command-predicate', which I knew about, since it's
mentioned in that blog post, but I forgot, so thanks for that!).
Best,
--
Marcin Borkowski
https://mbork.pl
https://crimsonelevendelightpetrichor.net/
next prev parent reply other threads:[~2024-11-11 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 19:36 How to get all commands defined in a specified file (or files)? mbork
2024-11-11 20:18 ` Eli Zaretskii
2024-11-11 20:38 ` [External] : " Drew Adams
2024-11-11 22:00 ` mbork
2024-11-11 23:33 ` Drew Adams
2024-11-11 21:58 ` mbork [this message]
2024-11-12 0:00 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-11-12 16:12 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-11-12 13:14 ` Eduardo Ochs
2024-11-13 23:46 ` Emanuel Berg
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=87r07hwhzn.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).