From: Dmitry Gutov <dgutov@yandex.ru>
To: Robert Pluim <rpluim@gmail.com>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: master fe939b3 1/2: Fix reference to `tags-loop-continue' in doc string
Date: Mon, 5 Aug 2019 13:42:34 +0300 [thread overview]
Message-ID: <baa602d7-ec3e-5f14-9d3d-b564823724dc@yandex.ru> (raw)
In-Reply-To: <m2ftmh87eb.fsf@gmail.com>
On 8/4/19 3:03 PM, Robert Pluim wrote:
> It begs the question why xrefs replaced a 'do the next thing' type
> binding with a 'go back' type binding in the first place.
Because it's more useful. The xref UI presents you with all matches
right away, and you choose before visiting, so you don't really need the
"go next" binding 98% of the time.
There's also 'next-error', which navigates between the matches too.
> Iʼm tempted
> to say that xref-pop-marker-stack should use a different binding, and
> M-, should be fileloop-continue, but the xref one has existed for 5
> years now.
Exactly. That ship has sailed. If you are still not convinced, please go
ahead and look up the older discussions for our reasoning.
next prev parent reply other threads:[~2019-08-05 10:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190801195403.16246.49802@vcs0.savannah.gnu.org>
[not found] ` <20190801195406.087AF20CC8@vcs0.savannah.gnu.org>
2019-08-02 8:59 ` master fe939b3 1/2: Fix reference to `tags-loop-continue' in doc string Robert Pluim
2019-08-02 10:49 ` Lars Ingebrigtsen
2019-08-02 12:23 ` Robert Pluim
2019-08-02 18:27 ` Lars Ingebrigtsen
2019-08-04 12:03 ` Robert Pluim
2019-08-04 12:09 ` Lars Ingebrigtsen
2019-08-04 12:24 ` Robert Pluim
2019-08-05 9:12 ` Lars Ingebrigtsen
2019-08-05 10:39 ` Dmitry Gutov
2019-08-05 10:46 ` Lars Ingebrigtsen
2019-08-05 10:54 ` Lars Ingebrigtsen
2019-08-05 13:12 ` Robert Pluim
2019-08-05 10:42 ` Dmitry Gutov [this message]
2019-08-05 15:05 ` Drew Adams
2019-08-05 18:50 ` Dmitry Gutov
2019-08-05 19:58 ` Juri Linkov
2019-08-07 18:33 ` Lars Ingebrigtsen
2019-08-07 22:11 ` Dmitry Gutov
2019-08-08 20:45 ` Juri Linkov
2019-08-06 3:23 ` Richard Stallman
2019-08-05 10:36 ` 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=baa602d7-ec3e-5f14-9d3d-b564823724dc@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
/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).