From: Radey Shouman <shouman@comcast.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 37820@debbugs.gnu.org, shouman@comcast.net
Subject: bug#37820: 25.2; xref using etags incorrect case fold during completion
Date: Fri, 17 Jan 2020 10:34:03 -0500 [thread overview]
Message-ID: <24097.54251.468235.835479@mothra.home> (raw)
In-Reply-To: <03310a1f-2505-7ec9-6791-94ee84f43ce4@yandex.ru>
Dmitry Gutov writes:
> On 17.01.2020 11:28, Eli Zaretskii wrote:
> > Can you tell what is the difference in user-facing behavior due to
> > this change? I'm not sure I understand that looking at the patch.
>
> Identifier completion in xref-find-definitions (C-u M-. TAB TAB), when
> the etags backend is in use, will honor the value of tags-case-fold-search.
I haven't looked at the patch yet, but I can describe the desired
change in user-facing behavior with an example:
Suppose tags-case-fold-search is true in a buffer with a tags table
containing the symbol "CamelCase".
The key sequence M.camelcase will find the definition of CamelCase.
On the other hand, with the current behavior, the key sequence M.cTAB
will show a completion buffer that does not contain "CamelCase".
With a proper fix, the completion buffer will include "CamelCase".
next prev parent reply other threads:[~2020-01-17 15: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 [this message]
2020-01-17 21:28 ` Dmitry Gutov
2020-01-18 22:33 ` Radey Shouman
2019-10-19 17:34 ` Radey Shouman
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
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=24097.54251.468235.835479@mothra.home \
--to=shouman@comcast.net \
--cc=37820@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).