unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Poll: Change xref-show-definitions-function's default?
Date: Mon, 4 Jan 2021 20:41:52 +0200	[thread overview]
Message-ID: <7b108ef2-7798-19b9-f37d-680bdcb23745@yandex.ru> (raw)
In-Reply-To: <871rf0ob2c.fsf@mail.linkov.net>

On 04.01.2021 19:42, Juri Linkov wrote:
>> In commit 8c383456291185b029b469061338b5b797a49747 I have done a bit of
>> cleanup and documented the existing alternative options.
>>
>> What do you say we make one of them the default?
> 
> As part of this poll we could also decide what to do with the TAB keybinding
> because especially after changing the value of 'xref-show-definitions-function'
> to 'xref-show-definitions-completing-read' and using the *xref* buffer
> exclusively for the grep-like output, it makes more sense for
> TAB to behave as in grep-mode.

No need to poll about that, I think.

As long as we change the default to one of the current two alternatives, 
TAB won't play any role in either (the -at-bottom function sets up RET 
to call the same command).

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.



  reply	other threads:[~2021-01-04 18:41 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 [this message]
2021-01-06 18:30     ` Juri Linkov
2021-01-06 20:55       ` Dmitry Gutov
2021-01-07 17:47         ` Juri Linkov
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=7b108ef2-7798-19b9-f37d-680bdcb23745@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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).