all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ludovic Brenta <ludovic@ludovic-brenta.org>
To: 32512@debbugs.gnu.org
Subject: bug#32512: xref--read-identifier using etags backend should honor case-fold-search
Date: Thu, 23 Aug 2018 17:11:18 +0100	[thread overview]
Message-ID: <4a1f6a0a6772940a66f0efd389535d96@ludovic-brenta.org> (raw)

Package: emacs
Version: 26.1
Severity: wishlist

Hello,

Suppose I have a file named foo-bar.adb containing:

package Foo.Bar is
end Foo.Bar;

and this has been tagged with etags, which is the backend in use for 
xref.

Now:
(a)
M-. foo.bar/b => jumps to foo-bar.adb line 1, "package Foo.Bar is".

but

(b)
M-. foo.bar <TAB> => "no match"

In (a), xref-find-definition took whatever my input was and honored
case-fold-search, which is t, to find the definition of the package.

But when I type <TAB> asking for possible completions, 
xref--read-identifier
is case-sensitive whether I like it or not.  Indeed:

(c)
M-. Foo.Bar <TAB> => produces the desired completion Foo.Bar/b

The inconsistency between (a) and (b) is anti-ergonomic.

I looked for a variable, separate from case-fold-search, that would
control the case sensitivity of completion in this case, but I couldn't
find one.

-- 
Ludovic Brenta.






             reply	other threads:[~2018-08-23 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 16:11 Ludovic Brenta [this message]
2018-08-23 17:29 ` bug#32512: xref--read-identifier using etags backend should honor case-fold-search Eli Zaretskii
2018-08-24 10:35   ` Ludovic Brenta
2018-08-24 12:35     ` Ludovic Brenta
2018-08-24 14:35       ` Helmut Eller
2021-09-01  9:47         ` Lars Ingebrigtsen
2021-09-01 17:42           ` Ludovic Brenta
2021-09-02  7:45             ` Lars Ingebrigtsen

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=4a1f6a0a6772940a66f0efd389535d96@ludovic-brenta.org \
    --to=ludovic@ludovic-brenta.org \
    --cc=32512@debbugs.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.