From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Mendler <mail@daniel-mendler.de>,
Lars Ingebrigtsen <larsi@gnus.org>,
22324@debbugs.gnu.org
Subject: bug#22324: 25.0.50; completion-category-defaults style doesn't override completion-styles (gets prepended instead)
Date: Fri, 28 Jan 2022 23:23:25 +0200 [thread overview]
Message-ID: <1b288d78-912d-b07d-3027-300b7ff10067@yandex.ru> (raw)
In-Reply-To: <jwv7daj7q6c.fsf-monnier+emacs@gnu.org>
On 28.01.2022 18:59, Stefan Monnier via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
> Dmitry Gutov [2022-01-28 04:37:36] wrote:
>> On 26.01.2022 15:36, Stefan Monnier via Bug reports for GNU Emacs, the Swiss
>> army knife of text editors wrote:
>>> We can probably have our cake and eat it too by adding a `fail`
>>> completion style. Such a style would always take responsibility
>>> (i.e. would never return nil to delegate to subsequent styles), but
>>> would always return a "useless" value that gives no completions.
>> *If* we did end up adding such style, would the default value of
>> completion-category-defaults include 'fail' at the end of its every line?
> No, since the fallback was chosen specifically for
> `completion-category-defaults`, we'd want to keep it for the cases that
> are already present at least.
Depends on how you look at it: out of 6 entries in there currently, I
added two of them, and since I was unaware of the fallback mechanism, it
wasn't quite intentional. Even if certain edge cases ended up using the
fallback to their benefit.
Knowing that now, I would probably rewrite those
completion-category-defaults to include all styles that would be tried
explicitly (meaning, add 'partial-completion' after 'substring').
next prev parent reply other threads:[~2022-01-28 21:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 20:27 bug#22324: 25.0.50; completion-category-defaults style doesn't override completion-styles (gets prepended instead) Dmitry Gutov
2016-01-08 12:17 ` Eli Zaretskii
2016-01-08 12:21 ` Dmitry Gutov
2016-01-08 12:26 ` Eli Zaretskii
2016-01-08 12:30 ` Dmitry Gutov
2016-01-08 15:31 ` Eli Zaretskii
2021-12-02 9:10 ` Lars Ingebrigtsen
2021-12-02 9:45 ` Eli Zaretskii
2021-12-06 1:16 ` Dmitry Gutov
2021-12-06 2:25 ` Lars Ingebrigtsen
2021-12-07 1:35 ` Dmitry Gutov
2021-12-07 20:28 ` Lars Ingebrigtsen
2021-12-07 22:46 ` Dmitry Gutov
2021-12-09 1:09 ` Lars Ingebrigtsen
2022-01-21 13:46 ` Lars Ingebrigtsen
2022-01-24 2:03 ` Dmitry Gutov
2022-01-24 9:46 ` Lars Ingebrigtsen
2022-01-25 2:27 ` Dmitry Gutov
2022-01-25 12:19 ` Lars Ingebrigtsen
2022-01-26 1:43 ` Dmitry Gutov
2022-01-26 2:31 ` Daniel Mendler
2022-01-26 13:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-26 13:49 ` Daniel Mendler
2022-01-26 17:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-26 18:59 ` Daniel Mendler
2022-01-26 22:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-26 23:32 ` Daniel Mendler
2022-01-27 6:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 2:35 ` Dmitry Gutov
2022-01-28 11:54 ` Daniel Mendler
2022-01-28 16:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 22:06 ` Dmitry Gutov
2022-01-28 23:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-29 1:57 ` Dmitry Gutov
2022-01-28 2:37 ` Dmitry Gutov
2022-01-28 16:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 21:23 ` Dmitry Gutov [this message]
2022-01-28 2:39 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b288d78-912d-b07d-3027-300b7ff10067@yandex.ru \
--to=dgutov@yandex.ru \
--cc=22324@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.