all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Drew Adams <drew.adams@oracle.com>,
	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 21:50:37 +0300	[thread overview]
Message-ID: <d149a264-82fd-55ce-a7f8-d6ebad368ba1@yandex.ru> (raw)
In-Reply-To: <068382bf-e781-4bd7-9a1d-df4857a6db0e@default>

On 8/5/19 6:05 PM, Drew Adams wrote:

> I would say "also useful" and "differently useful",
> or "sometimes more useful" - not "more useful".
> 
> Is `occur' (show all matches, let you get directly
> to any, in any order) more useful than incremental
> search?

The question was about xref, not general Emacs usage. Since M-. is bound 
to xref-find-definitions, M-, should do the action that makes most sense 
for the former.

> But I also recognize that a single tool - even a
> good, flexible one - is not necessarily the best
> tool for all jobs.

That is true, and we provide different commands and ways of interaction. 
But the number of useful, short key bindings is limited, and we have to 
make a good, consistent choices in that regard that would benefit the 
most users.

> But why is it too late to rehabilitate the
> `do the next thing' commands and their doc,
> and give them key bindings once again?  Why
> promote only `xref', essentially deprecating
> the others?

I'm not seeing a specific proposal, like which keys exactly would you 
want to use. Maybe make a bug report specifically about that.

IIRC pop-tag-mark was bound to 'M-*'? It seems unused.

> Why not promote (document, bind, etc.) both
> approaches?  We don't denigrate Isearch just
> because we have `occur'.

Because bindings loads of different commands to many different, long 
keybindings is not as useful as some people seem to think.

> I'm convinced of the utility of `xref' (and
> I always was).  I'm not convinced that the
> existing commands/keys had to be sacrificed
> in order to promote what you see as "more
> useful" (even perhaps as best for all uses).

I wouldn't say that any commands were sacrificed.



  reply	other threads:[~2019-08-05 18:50 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d149a264-82fd-55ce-a7f8-d6ebad368ba1@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=drew.adams@oracle.com \
    --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 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.