From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: master adfcc17: * lisp/vc/vc-dir.el: Commands to mark un/registered files (bug#34949)
Date: Mon, 06 Apr 2020 01:50:32 +0300 [thread overview]
Message-ID: <87y2r9wnrb.fsf@mail.linkov.net> (raw)
In-Reply-To: <52a199f7-919f-4dd0-8c94-25e6b0cf7ea5@default> (Drew Adams's message of "Sat, 4 Apr 2020 17:51:53 -0700 (PDT)")
> I gave reasons for not conflicting with Dired bindings,
> if VC Dired is derived from Dired, and especially if
> such bindings make sense also for VC Dired.
>
> But there can be other, opposing reasons to repurpose
> a given Dired binding, again especially if the Dired
> binding is not so useful in VC Dired.
>
> There's no hard and fast rule, IMO. Such things are
> judgment calls, after weighing pros & cons. It's you
> who should decide what to do here, for VC Dired.
Ok, then I'd leave this to Dmitry to decide what to do here,
because currently I'm already completely satisfied with
the new keybinding for marking registered files that was
too cumbersome to do earlier when it required marking
separately each of file types (added, removed, edited :)
next prev parent reply other threads:[~2020-04-05 22:50 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
2020-04-05 0:51 ` Drew Adams
2020-04-05 22:50 ` Juri Linkov [this message]
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=87y2r9wnrb.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=dgutov@yandex.ru \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--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).