unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Morgan Willcock <morgan@ice9.digital>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,   emacs-devel@gnu.org
Subject: Re: TAGS completion with (setq-local completion-ignore-case t)
Date: Wed, 13 Mar 2024 00:09:16 +0000	[thread overview]
Message-ID: <87cyrzuh5f.fsf@ice9.digital> (raw)
In-Reply-To: <861q8jxv5m.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 09 Mar 2024 17:49:25 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> > Why exactly do you need to have a buffer-local value of
>> > completion-ignore-case?  This is not a user option, and is meant to be
>> > either set globally or let-bound for specific code.
>>
>> I was using it as a configuration example for a major-mode setup hook,
>> where the language itself is not case-sensitive, but completions through
>> capf functions (including TAG completion) can be displayed and inserted
>> in mixed case.
>>
>> Is there a supported way to have user configurable case-insensitive
>> completion that is configured per major mode?
>
> use the user options specific for each type of completion, I'd say.
> For TAGS that's tags-case-fold-search; for file names that's
> read-file-name-completion-ignore-case; for buffers its
> read-buffer-completion-ignore-case.  And there may be others.
>
> Stefan, any better ideas?

I've tested wrapping the capf functions with Cape's cape-capf-case-fold
transformer.  This seems to give the ideal result for the actual
completions and is fine to be restricted to the major-mode (the wrapped
version is just another capf function which can be buffer-local).

https://elpa.gnu.org/packages/cape.html

I'll likely stick with this solution because it works so well, but thank
you for looking at the built-in options.

-- 
Morgan Willcock



      parent reply	other threads:[~2024-03-13  0:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07  9:14 TAGS completion with (setq-local completion-ignore-case t) Morgan Willcock
2024-03-07  9:45 ` Eli Zaretskii
2024-03-07  9:54   ` Morgan Willcock
2024-03-07 10:49     ` Eli Zaretskii
2024-03-07 11:37       ` Morgan Willcock
2024-03-09  7:51         ` Eli Zaretskii
2024-03-09 13:23           ` Morgan Willcock
2024-03-09 13:30             ` Eli Zaretskii
2024-03-09 14:06               ` Morgan Willcock
2024-03-09 14:26                 ` Eli Zaretskii
2024-03-09 14:33                   ` Morgan Willcock
2024-03-09 14:46                     ` Eli Zaretskii
2024-03-09 14:36                   ` Eli Zaretskii
2024-03-09 14:57                     ` Morgan Willcock
2024-03-09 15:49                       ` Eli Zaretskii
2024-03-09 15:56                         ` Eli Zaretskii
2024-03-13  0:09                         ` Morgan Willcock [this message]

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=87cyrzuh5f.fsf@ice9.digital \
    --to=morgan@ice9.digital \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 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).