unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: How to get all commands defined in a specified file (or files)?
Date: Mon, 11 Nov 2024 20:38:42 +0000	[thread overview]
Message-ID: <BLAPR10MB5219F63751D900F25625F4A7F3582@BLAPR10MB5219.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86ttcdikwz.fsf@gnu.org>

> > 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.

Maybe also...

Has the file been loaded, so the commands are already defined?
Or are they at least autoloaded?
Does the file use a library-specific prefix for all of its
function names?

If so, you can filter all commands (`commandp') according
to that library prefix.



  reply	other threads:[~2024-11-11 20:38 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   ` Drew Adams [this message]
2024-11-11 22:00     ` [External] : " mbork
2024-11-11 23:33       ` Drew Adams
2024-11-11 21:58   ` mbork
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=BLAPR10MB5219F63751D900F25625F4A7F3582@BLAPR10MB5219.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --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).