emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Current mode command discovery


From: Eli Zaretskii
Subject: Re: Current mode command discovery
Date: Sat, 20 Feb 2021 17:23:16 +0200

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 20 Feb 2021 15:51:18 +0100
> 
> >   Click on a completion to select it.
> >   In this buffer, type RET to select the completion near point.
> >
> >   Possible completions are:
> >   backward-delete-char-untabify (DEL)               completion-at-point 
> > (C-M-i)
> >   edebug-defun (edebug-eval-top-level-form)
> >   eval-defun (C-M-x)                                eval-print-last-sexp 
> > (C-j)
> >   indent-pp-sexp (C-M-q)
> >
> > That's it.  All of it.  Is that the intent?
> 
> Yup.  Well, `lisp-interaction-mode' hasn't been tagged up, so you're
> basically getting `C-h m' in `M-x'-like form.  I'm not sure `M-S-x' in
> the *scratch* buffer will ever include more than that, but this command
> is (well, will be) more useful for command discovery in more specialised
> modes.

Really?  I thought the intent was to filter _out_ those commands that
are not relevant.  If the intent is to filter _in_, then won't this
omit many important commands?

IOW, what is the use case for completing _only_ on the commands that
were tagged as being relevant for the current major mode?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]