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: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: master adfcc17: * lisp/vc/vc-dir.el: Commands to mark un/registered files (bug#34949)
Date: Sun, 5 Apr 2020 03:04:05 +0300	[thread overview]
Message-ID: <4b222ce3-6493-7057-e631-2e2c78c2de2b@yandex.ru> (raw)
In-Reply-To: <874ktybzss.fsf@mail.linkov.net>

On 05.04.2020 02:33, Juri Linkov wrote:
>> I rather meant binding to 'r' directly instead of '* r' if we only add
>> one binding.
> '*' has nice mnemonic of the verb "mark" (used in Dired as well), so
> '* r' means "mark registered (files)".  The prefix will allow more keys.
> 
>> With '* r', we can just as well add '* u' now. Up to you, of course.
> '* u' was not added because Drew opposed on the ground that it will
> conflict with the same keybinding in Dired where it is bound to
> 'dired-unmark'.

So we "can add more keys", but at the same time can't add the most 
likely current candidate?

Why don't we go ahead and pick one of the stools.



  reply	other threads:[~2020-04-05  0:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200402220815.6555.35405@vcs0.savannah.gnu.org>
     [not found] ` <20200402220817.0DD6F20CDD@vcs0.savannah.gnu.org>
2020-04-03 15:22   ` master adfcc17: * lisp/vc/vc-dir.el: Commands to mark un/registered files (bug#34949) Stefan Monnier
2020-04-03 16:09     ` Dmitry Gutov
2020-04-04 23:33       ` Juri Linkov
2020-04-05  0:04         ` Dmitry Gutov [this message]
2020-04-05  0:51         ` Drew Adams
2020-04-05 22:50           ` Juri Linkov
2020-04-06  0:02             ` Dmitry Gutov
2020-04-06 23:51               ` Juri Linkov
2020-04-10  3:39                 ` 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=4b222ce3-6493-7057-e631-2e2c78c2de2b@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=monnier@iro.umontreal.ca \
    /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).