From: Nick Roberts <nickrob@snap.net.nz>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: VC state
Date: Wed, 9 Apr 2008 15:52:11 +1200 [thread overview]
Message-ID: <18428.15723.176227.750017@kahikatea.snap.net.nz> (raw)
In-Reply-To: <200804090307.m3937emd022768@sallyv1.ics.uci.edu>
> > I don't see it as particularly experimental: it's what I now use as
> > a replacement for PCL-CVS when I use Bzr.
>
> So can the experimental label be removed then?
> How about binding vc-status to C-x v d so that it gets more exposure?
> What is the plan for vc-dired?
> When can it be removed?
> IMO it does not make sense to keep code for two different
> implementations of the same thing, it just adds complexity to the code.
Any "experimental label" is in the mind, so consider it already removed.
If vc-status is meant to be an improved replacement for vc-dired then
it seems reasonable to me that it takes the binding 'C-x v d'. However,
I still use vc-dired so I think it's unreasonable to remove vc-dired
until vc-status does everything better.
I've only briefly looked at vc-status but here are a few things that I
noticed:
* vc-status doesn't seem to heed vc-stay-local or vc-cvs-stay-local.
* The filenames are highlighted by the mouse but clicking mouse-2 doesn't
visit the file in another buffer
* The statuses are highlighted by the mouse but clicking mouse-2 doesn't
do anything special
* The bindings vc-status-previous/next-line are on the menubar as menu-items
but no-one would ever use them from there.
* I'm not sure if the keybindings are based on Dired or Pcl-cvs but they
seem to be an unmemorable mix of upper and lowercase letters and other
characters.
* If Emacs can't connect with the server there is no message in the buffer
or elsewhere to explain what has happened.
* There is no description in the manual for vc-status. Indeed the node
"VC Status" is about Log-View mode.
* The mode name is "*VC Status*". I think the convention of enclosing
names in asterisks is for buffer names only.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2008-04-09 3:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 5:54 VC state Stefan Monnier
2008-04-06 17:40 ` Dan Nicolaescu
2008-04-07 15:16 ` Stefan Monnier
2008-04-08 15:03 ` conflict state (was Re: VC state) Dan Nicolaescu
2008-04-09 20:35 ` conflict state Stefan Monnier
2008-04-09 21:39 ` Dan Nicolaescu
2008-04-10 0:44 ` Stefan Monnier
2008-04-08 20:45 ` VC state Dan Nicolaescu
2008-04-09 2:44 ` Stefan Monnier
2008-04-09 3:07 ` Dan Nicolaescu
2008-04-09 3:52 ` Nick Roberts [this message]
2008-04-09 22:54 ` Dan Nicolaescu
2008-04-10 5:53 ` VC development [was Re: VC state] Nick Roberts
2008-04-10 8:33 ` VC state Nick Roberts
2008-04-10 14:13 ` Dan Nicolaescu
2008-04-11 12:01 ` Nick Roberts
2008-04-10 19:17 ` Stefan Monnier
2008-04-09 14:02 ` Stefan Monnier
2008-04-10 17:28 ` Dan Nicolaescu
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=18428.15723.176227.750017@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=dann@ics.uci.edu \
--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 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.