From: Winston <wbe@psr.com>
To: Eli Zaretskii <eliz@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>
Cc: wbe@psr.com, 28439@debbugs.gnu.org
Subject: bug#28439: suggestion: support case-independent xref-find-definitions prompt
Date: Wed, 27 Sep 2017 19:07 EDT [thread overview]
Message-ID: <201709272307.v8RN7Jdb099103@psr.com> (raw)
In-Reply-To: <201709122237.v8CMb6w0029533@psr.com>
Re: using completion-ignore-case to control both completions and
xref-find-definitions
Dmitry previously commented:
> We can do that without an extra variable, though, by making
> definitions search be controlled by completion-ignore-case.
Unless you want to argue that xref-find-definitions is a
"completion", doing that would mean that completion-ignore-case has an
unexpected side-effect (namely, that it affects a function that is not a
"completion"). On programming aesthetic grounds, then, I'd argue that
xref-ignore-case (or whatever you want to call it) would be better.
-WBE
next prev parent reply other threads:[~2017-09-27 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 22:37 bug#28439: suggestion: support case-independent xref-find-definitions prompt TAB Winston
2017-09-12 23:24 ` Stephen Berman
2017-09-12 23:31 ` bug#28439: suggestion: support case-independent xref-find-definitions Winston
2017-09-13 15:30 ` bug#28439: suggestion: support case-independent xref-find-definitions prompt TAB Eli Zaretskii
2017-09-13 23:04 ` Dmitry Gutov
2017-09-14 17:01 ` Eli Zaretskii
2017-09-19 0:55 ` Dmitry Gutov
2017-09-19 4:01 ` Eli Zaretskii
2017-09-14 18:21 ` bug#28439: suggestion: support case-independent xref-find-definitions prompt Winston
2017-09-14 22:05 ` Dmitry Gutov
2017-09-14 22:33 ` bug#28439: suggestion: support case-independent Winston
2017-09-19 0:41 ` Dmitry Gutov
2017-09-27 23:07 ` Winston [this message]
2017-09-28 20:47 ` bug#28439: suggestion: support case-independent xref-find-definitions prompt Dmitry Gutov
2020-09-15 15:20 ` 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=201709272307.v8RN7Jdb099103@psr.com \
--to=wbe@psr.com \
--cc=28439@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--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.