unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Poll: Change xref-show-definitions-function's default?
Date: Thu, 07 Jan 2021 19:47:07 +0200	[thread overview]
Message-ID: <87h7nsslqk.fsf@mail.linkov.net> (raw)
In-Reply-To: <07c6166d-119a-6479-03ed-2bde5c51959f@yandex.ru> (Dmitry Gutov's message of "Wed, 6 Jan 2021 22:55:21 +0200")

>> I'm afraid the default of xref-show-definitions-function can't be changed
>> to xref-show-definitions-completing-read because as this poll indicates
>> it works satisfactorily only in combination with icomplete-mode and
>> also non-nil icomplete-show-matches-on-no-input.
>
> What about xref-show-definitions-buffer-at-bottom, then?

Sorry, I have no opinion about xref-show-definitions-buffer-at-bottom,
I'm using xref-show-definitions-completing-read with icomplete.

>>> Then we can safely remove/change the TAB binding in xref--xref-buffer-mode,
>>> or alternatively, create a new major mode that is slightly more Grep-like,
>>> and use it in the default xref-show-xrefs-function.
>> Maybe a new submode could help to resolve this discrepancy.
>
> Yes, that's the second option I meant.

Maybe the TAB keybinding should depend on the value of
xref-show-definitions-function.  When it is customized to
xref-show-definitions-completing-read then don't bind TAB.



  reply	other threads:[~2021-01-07 17:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 18:28 Poll: Change xref-show-definitions-function's default? Dmitry Gutov
2020-12-30  3:17 ` Lars Ingebrigtsen
2020-12-31 13:06 ` Daniel Martín
2021-01-01 12:25   ` Zhiwei Chen
2021-01-01 12:46     ` Dmitry Gutov
2021-01-01 13:33   ` Dmitry Gutov
2021-01-02 21:09   ` João Távora
2021-01-03 23:54     ` Daniel Martín via "Emacs development discussions.
2021-01-03 23:58       ` João Távora
2021-01-04  0:07         ` Dmitry Gutov
2021-01-04  8:48           ` João Távora
2021-01-04 11:16             ` Dmitry Gutov
2021-01-04 11:24               ` João Távora
2021-01-04 11:42                 ` Dmitry Gutov
2021-01-01  7:59 ` martin rudalics
2021-01-01 12:17   ` Dmitry Gutov
2021-01-02 10:26   ` Philip K.
2021-01-02 15:43     ` martin rudalics
2021-01-02 17:25       ` Dmitry Gutov
2021-01-03  8:39         ` martin rudalics
2021-01-03 17:43           ` Dmitry Gutov
2021-01-02 10:24 ` Philip K.
2021-01-02 11:08   ` Dmitry Gutov
2021-01-04 12:12 ` Philip K.
2021-01-04 12:22   ` Dmitry Gutov
2021-01-04 14:21     ` Philip K.
2021-01-04 16:14       ` Dmitry Gutov
2021-01-04 17:42 ` Juri Linkov
2021-01-04 18:41   ` Dmitry Gutov
2021-01-06 18:30     ` Juri Linkov
2021-01-06 20:55       ` Dmitry Gutov
2021-01-07 17:47         ` Juri Linkov [this message]
2021-01-09  0:35           ` 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=87h7nsslqk.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@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 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).