From: Stephen Berman <stephen.berman@gmx.net>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Show all completions based on substring search
Date: Wed, 09 Nov 2022 23:29:25 +0100 [thread overview]
Message-ID: <87k0433goq.fsf@rub.de> (raw)
In-Reply-To: <m2v8nnlrpf.fsf@me.com> ("Rudolf Adamkovič"'s message of "Wed, 09 Nov 2022 22:54:04 +0100")
On Wed, 09 Nov 2022 22:54:04 +0100 Rudolf Adamkovič <salutis@me.com> wrote:
> Howdy smart folks!
>
> I noticed that Emacs (v29, 5b9b393c61) does not always show all
> completions, the way I would like.
>
> Given
>
> 1. emacs -Q
> 2. C-h f
> 3. warning TAB,
>
> I get the following 3 completions:
>
> warning-numeric-level
> warning-suppress-p
> warnings-suppress
>
> Instead, I would like to see all candidates that contain the substring
> `warning', such as `display-warning'.
>
> I noticed that if I move the point to the beginning of the word
> `warning' and type `TAB' there, then I get all candidates that contain
> the substring `warning', including `display-warning'.
>
> How can make the completion system *always* do this on `TAB', without
> moving the point? (Or using word completion, or typing the Orderless
> separator, or anything else like that.)
Typing `*warning TAB' works for me - after setting
`completion-category-overrides' to ((buffer (styles substring)) (file
(styles substring))). With -Q that variable's value is nil, and there
typing `*warning TAB' immediately completes to `*-warning', so another
TAB does not show function names beginning with `warning-'. That
setting overrides for buffer and file name completion is apparently
needed for function name completion is not something I expected...
Steve Berman
next prev parent reply other threads:[~2022-11-09 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 21:54 Show all completions based on substring search Rudolf Adamkovič
2022-11-09 22:29 ` Stephen Berman [this message]
2022-11-18 17:49 ` Rudolf Adamkovič
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=87k0433goq.fsf@rub.de \
--to=stephen.berman@gmx.net \
--cc=help-gnu-emacs@gnu.org \
--cc=salutis@me.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.
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).