unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>, Juri Linkov <juri@linkov.net>
Cc: Robert Pluim <rpluim@gmail.com>,
	Drew Adams <drew.adams@oracle.com>,
	emacs-devel@gnu.org
Subject: Re: master fe939b3 1/2: Fix reference to `tags-loop-continue' in doc string
Date: Thu, 8 Aug 2019 01:11:14 +0300	[thread overview]
Message-ID: <da53089f-50a4-ae7d-de81-8a6839e3e245@yandex.ru> (raw)
In-Reply-To: <871rxw9672.fsf@mouse.gnus.org>

On 07.08.2019 21:33, Lars Ingebrigtsen wrote:
> Juri Linkov <juri@linkov.net> writes:
> 
>> M-. runs the command xref-find-definitions
>> M-, runs the command xref-pop-marker-stack
>> C-M-. runs the command xref-find-apropos
>> C-M-, is undefined
>>
>> so C-M-, is free to use for fileloop-continue
> 
> That seems like a logical key binding for that command.

Even though it's not related to any of the other commands in the list above?

I'm not really against it, but it doesn't sound particularly "logical".

M-*, on the other hand, seems somewhat pertinent: an asterisk is usually 
related to a set of items, and e.g. in Vim '*' jumps between occurrences 
of a symbol.



  reply	other threads:[~2019-08-07 22:11 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
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 [this message]
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=da53089f-50a4-ae7d-de81-8a6839e3e245@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --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).