From: Radey Shouman <shouman@comcast.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37820@debbugs.gnu.org, Radey Shouman <shouman@comcast.net>
Subject: bug#37820: 25.2; xref using etags incorrect case fold during completion
Date: Sat, 19 Oct 2019 13:34:10 -0400 [thread overview]
Message-ID: <23979.18706.640623.17645@mothra.home> (raw)
In-Reply-To: <83wod16xa0.fsf@gnu.org>
Eli Zaretskii writes:
> > Date: Fri, 18 Oct 2019 20:13:31 -0400
> > From: Radey Shouman <shouman@comcast.net>
> > Cc: shouman@comcast.net
> >
> > In order to reproduce the bug, set tags-case-fold-search to t,
> > completion-ignore-case to nil
>
> Isn't that a contradiction of sorts? How can we know which of these
> two should have precedence?
I would expect that you would follow the precedent of find-tag, which
uses tags-case-fold-search and case-fold-search to determine whether
a tags search is case-sensitive or not.
Whether case should be folded during completion seems dependent on the
application; I have never been tempted to change the default value of
completion-ignore-case -- the note on that variable was included because
setting it to non-nil would prevent observing the bug. From a quick look
at the lisp directory completion-ignore-case is typically used by binding
it during a completion.
The info file says:
You can control the case-sensitivity of tags search commands by
customizing the value of the variable ‘tags-case-fold-search’. The
default is to use the same setting as the value of ‘case-fold-search’
(*note Search Case::).
I found it surprising that completion would not follow the tags search
itself in folding case, as I have become used to this useful behavior
over many years of using find-tag.
next prev parent reply other threads:[~2019-10-19 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 0:13 bug#37820: 25.2; xref using etags incorrect case fold during completion Radey Shouman
2019-10-19 6:53 ` Eli Zaretskii
2019-10-19 7:14 ` Dmitry Gutov
2019-10-19 17:40 ` Radey Shouman
2019-10-25 13:59 ` Radey Shouman
2019-12-25 0:45 ` Dmitry Gutov
2019-12-26 20:56 ` Radey Shouman
[not found] ` <abb85c0d-b89d-d82a-836e-f1e2755fa149@yandex.ru>
2020-01-17 8:28 ` Eli Zaretskii
2020-01-17 12:49 ` Dmitry Gutov
2020-01-17 13:39 ` Eli Zaretskii
2020-01-17 21:29 ` Dmitry Gutov
2020-01-17 15:34 ` Radey Shouman
2020-01-17 21:28 ` Dmitry Gutov
2020-01-18 22:33 ` Radey Shouman
2019-10-19 17:34 ` Radey Shouman [this message]
2019-10-19 21:07 ` Drew Adams
2019-10-20 16:19 ` 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=23979.18706.640623.17645@mothra.home \
--to=shouman@comcast.net \
--cc=37820@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.