From: Morgan Willcock <morgan@ice9.digital>
To: Eshel Yaron <me@eshelyaron.com>
Cc: 73234@debbugs.gnu.org
Subject: bug#73234: 30.0.91; completion-preview-mode doesn't trigger for case-insensitive capf
Date: Wed, 18 Sep 2024 21:23:44 +0100 [thread overview]
Message-ID: <87cyl04sof.fsf@ice9.digital> (raw)
In-Reply-To: <m1zfo685lz.fsf@dazzs-mbp.home> (Eshel Yaron's message of "Tue, 17 Sep 2024 21:03:52 +0200")
Eshel Yaron <me@eshelyaron.com> writes:
> FYI, I've added a new user option completion-preview-ignore-case on the
> master branch (commit f1794a17b62), which controls case sensitivity for
> Completion Preview mode specifically. This is definitely safe to set
> buffer-locally. The docstring of this new variable should hopefully
> also explain exactly what's the expected behavior in this regard.
Thanks for adding the new option. For my use case I don't think I would
be able to use it because the case mismatch between the text already
typed and the completion will effectively be generating a completion
which may not actually exist.
e.g. If a valid completion was "FooBar", and I typed "foo", having the
final result as "fooBar" wouldn't be ideal.
I've been trying to think of a way to get it to work without disturbing
the user interface that already exists. Maybe it would be possible
fixup the result in a post-insertion hook if one existed - such a hook
might be generally useful anyway.
In the long term though, I really think that the preview should be
allowed to overlap with the text already typed and potentially replace
it when the completion is inserted, but I appreciate that it would be a
big change in the internals to please a minority.
Morgan
--
Morgan Willcock
next prev parent reply other threads:[~2024-09-18 20:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 19:23 bug#73234: 30.0.91; completion-preview-mode doesn't trigger for case-insensitive capf Morgan Willcock
2024-09-14 6:07 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 9:53 ` Morgan Willcock
2024-09-14 16:23 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 20:46 ` Morgan Willcock
2024-09-15 6:40 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-17 19:03 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-18 20:23 ` Morgan Willcock [this message]
2024-09-19 5:39 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 14:59 ` Morgan Willcock
2024-09-20 9:27 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-20 10:05 ` Morgan Willcock
2024-09-20 10:34 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87cyl04sof.fsf@ice9.digital \
--to=morgan@ice9.digital \
--cc=73234@debbugs.gnu.org \
--cc=me@eshelyaron.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).