From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master 927b885 1/3: Disable filtering of commands in M-x completion
Date: Thu, 18 Feb 2021 16:25:45 +0000 [thread overview]
Message-ID: <SA2PR10MB4474BCAA9FCF73649B64B76AF3859@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87sg5toh2y.fsf@mail.linkov.net>
> >> I'd like also to suggest to filter out commands
> >> having "r" in their interactive specs - they signal
> >> an error when the region is not active, so no
> >> need to show them.
> >
> > Are you sure they raise an error?
> >
> > (defun foo (&optional beg end)
> > (interactive "r")
> > (message "FOO"))
>
> Yes, I'm sure. 'M-x foo RET' without an active region
> raises an error:
> command-execute: The mark is not active now
I don't see that in Emacs 27.1 or prior (with
`emacs -Q'). Is this perhaps new for 28?
If so, why would we do that?
`interactive' code `r' gives you the region
limits, regardless of whether the region is
active - which is TRT.
I don't understand why this should now raise an
error (even if `r' gave you the limits only when
the region were active - which it shouldn't).
And certainly in a case like the example I gave,
where the args are optional. I don't see the
motivation for now raising an error.
> > I also think it's misleading to base filtering on
> > an `interactive' form that uses a string. That's
> > inherently fragile/limiting. It won't apply to a
> > form that evaluates a sexp to provide the args.
> > The resulting incoherence will confuse users.
>
> This means that more complex interactive specs
> need manual tagging using a new tag:
> (declare (predicate (use-region-p)))
That's not what `r' has done forever (up through
Emacs 27.1, at least). It's never been only about
the _active_ region.
Anyway, that's only for `r'. You can no doubt
propose something for other `interactive' codes.
But even that won't handle arbitrary `interactive'
sexps, right?
`interactive' can accept a string arg, which, in
effect, has its own, parsable language. So you
can try to parse, and try to do some somewhat
relevant tagging based on that parsing.
But `interactive' is much more general than what's
represented by that string-arg language. Trying
to base your tagging on `interactive' seems
fundamentally flawed/misguided.
> >> Also filter out commands with "*" in read-only buffers.
> > Same problem. Relying on a string arg to `interactive'
> > is not a great idea, I think.
>
> Same tag:
> (declare (predicate (not buffer-read-only)))
And what about commands that might be usable
interactively, but whose `interactive' spec
doesn't encapsulate all that's involved? In that
case, manual addition of a declaration will need
to look into the logic of the command body as
well. (Admittedly, such commands are uncommon.)
> >> `describe-command' is a very good idea for searching
> >> and discovering commands.
> >
> > I mentioned that I defined that long ago. But I'll
> > also mention that `describe-function' with a prefix
> > arg already gives you that behavior. Oops! Nope,
> > that too is something I defined long ago in
> > `help-fns+.el'.
> >
> > Similarly, I defined `describe-option', and a prefix
> > arg to (my definition of) `describe-variable' limits
> > choices to user options (like `describe-option').
>
> Using a prefix arg for 'C-h f' and 'C-h v' to limit the list
> of completions would be nice.
>
> But I guess M-x can't use a prefix arg to limit completions?
Why do you think so? `C-u M-x describe-function TAB'
(with my definition from `help-fns+.el') shows only
commands as candidates.
next prev parent reply other threads:[~2021-02-18 16:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210217165944.26910.26583@vcs0.savannah.gnu.org>
[not found] ` <20210217165946.030D420DFC@vcs0.savannah.gnu.org>
2021-02-17 19:27 ` master 927b885 1/3: Disable filtering of commands in M-x completion Stefan Kangas
2021-02-17 20:01 ` Juri Linkov
2021-02-17 22:18 ` [External] : " Drew Adams
2021-02-18 9:33 ` Juri Linkov
2021-02-18 16:25 ` Drew Adams [this message]
2021-02-18 17:22 ` Juri Linkov
2021-02-18 18:24 ` Drew Adams
2021-02-18 19:03 ` Juri Linkov
2021-02-18 19:18 ` Drew Adams
2021-02-18 19:35 ` Eli Zaretskii
2021-02-18 19:47 ` Drew Adams
2021-02-18 19:58 ` Eli Zaretskii
2021-02-18 20:11 ` Drew Adams
2021-02-18 20:22 ` Drew Adams
2021-02-18 20:25 ` Eli Zaretskii
2021-02-18 20:45 ` Drew Adams
2021-02-19 13:17 ` Eli Zaretskii
2021-02-19 17:53 ` Drew Adams
2021-02-19 18:38 ` Eli Zaretskii
2021-02-18 23:15 ` martin rudalics
2021-02-18 23:32 ` Drew Adams
2021-02-19 8:37 ` Eli Zaretskii
2021-02-19 17:42 ` Drew Adams
2021-02-18 19:38 ` Eli Zaretskii
2021-02-18 19:49 ` Drew Adams
2021-02-18 19:58 ` Eli Zaretskii
2021-02-18 20:26 ` Drew Adams
2021-02-17 20:04 ` Eli Zaretskii
2021-02-17 20:31 ` Stefan Kangas
2021-02-17 20:12 ` [External] : " Drew Adams
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=SA2PR10MB4474BCAA9FCF73649B64B76AF3859@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=stefankangas@gmail.com \
/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).