From: Ivan Shmakov <ivan@siamics.net>
To: 12492@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: bug#12492: vc-dir vs. vc-root-dir
Date: Wed, 21 Jan 2015 20:55:11 +0000 [thread overview]
Message-ID: <87sif3rh00.fsf@violet.siamics.net> (raw)
In-Reply-To: <505E43E1.9090801@yandex.ru> (Dmitry Gutov's message of "Sun, 23 Sep 2012 03:04:01 +0400")
>>>>> Dmitry Gutov <dgutov@yandex.ru> writes:
[…]
> 2) For almost all backends we can easily deduce the repository root
> directory (exceptions: cvs, rcs, sccs), and I believe that in almost
> all cases the user wants to see the status of this directory, not of
> some subdirectory or any directory unrelated to the current buffer.
> Hence the function vc-root-dir, which I think should be bound to 'C-x
> v d' and the respective menu item. In the rare case when the user
> need to do something unusual, they can do M-x vc-dir.
We already have at least two pairs of commands (C-x v l vs.
C-x v L /and/ C-x v = vs. C-x v D), of which one operates on the
current file /and/ the other on the repository as a whole.
Is there any good reason we can’t have a similar arrangement for
vc-dir (C-x v d) and the proposed vc-root-dir command (say,
C-x v /, – where ‘/’ is a kind of obvious mnemonic for “root”)?
I find it way better than f302475471df, as it both keeps the
current behavior for C-x v d for those who may still want it
/and/ it offers a /prompt-free/ shortcut for those who’d always
want to use vc-dir on the root.
> When the backend doesn't have the function vc-xx-root, vc-root-dir
> interactively delegates to vc-dir, so for CVS, for example, the
> behavior will not change.
That’s certainly sensible, too.
[…]
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next parent reply other threads:[~2015-01-21 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <505E43E1.9090801@yandex.ru>
2015-01-21 20:55 ` Ivan Shmakov [this message]
[not found] ` <871rzer8t2.fsf@mail.linkov.net>
[not found] ` <8d51a8c9-6200-84c9-cadb-09576b060fe1@yandex.ru>
[not found] ` <87o92h7fv1.fsf@mail.linkov.net>
[not found] ` <c077c5d4-c343-a902-d184-1aa66f40eb07@yandex.ru>
[not found] ` <m38stkzoba.fsf@gnus.org>
[not found] ` <878stissii.fsf@mail.linkov.net>
[not found] ` <m34l44a9vk.fsf@gnus.org>
[not found] ` <87muhtzh8z.fsf@mail.linkov.net>
[not found] ` <875zfvzfvp.fsf@mail.linkov.net>
[not found] ` <8772f3cb-5af2-f89a-db47-682d9feef125@yandex.ru>
[not found] ` <87lfoqjr20.fsf@mail.linkov.net>
[not found] ` <ef584215-0515-ac7a-4f3c-d7cd3d17b0d5@yandex.ru>
[not found] ` <87y2slup32.fsf@mail.linkov.net>
[not found] ` <318f40f9-78ae-d739-6ac8-b7bb04598aad@yandex.ru>
[not found] ` <877e022uul.fsf@mail.linkov.net>
[not found] ` <3c0c8d61-1df2-b481-655a-d0b610ee6324@yandex.ru>
[not found] ` <8736ap10x9.fsf@mail.linkov.net>
[not found] ` <3631ca1d-9a11-8ff6-08bb-6d18268e47d2@yandex.ru>
[not found] ` <87r1y7odxt.fsf@mail.linkov.net>
[not found] ` <a51ea0fb-e8a1-9a71-7ce2-3c49ee25289c@yandex.ru>
[not found] ` <87ftemuzd6.fsf@mail.linkov.net>
2020-03-06 15:24 ` "Non-standard UI", was: Re: bug#12492: Acknowledgement (24.2.50; Open vc-dir buffer easier and faster) Dmitry Gutov
2020-03-08 0:53 ` "Non-standard UI", Juri Linkov
2020-03-08 10:38 ` "Non-standard UI" 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=87sif3rh00.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=12492@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
/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).