all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Masatake YAMATO <jet@gyve.org>, emacs-devel@gnu.org
Subject: Re: vc-dired
Date: Mon, 23 Jul 2007 11:18:35 -0700	[thread overview]
Message-ID: <200707231818.l6NIIZe3011091@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <jwvfy3huo8t.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat\, 21 Jul 2007 23\:12\:39 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

  > >> I was interested in merge DVC to GNU Emacs. However, these days, I am
  > >> busy and I get interests to extend vc-dired, so I've just asked DVC
  > >> developers to assign another people for working on the merging task.
  > 
  > > Given that you are interested in vc-dired, can you please look into
  > > these issues: 
  > 
  > > - pass --ignore= to ls so that it does not recurse into things like
  > >   .svn directories
  > 
  > At least the vc.el part of VC should simply not use `ls' or any such thing
  > and shouldn't recurse into directories.  It should simply ask the backend to
  > do it (the backend can then use "cvs -n update" or "svn status" ...).
  > That'll be blindingly faster.

I would go even farther, IMVHO the "dired" part of the interface for
vc-dired is not that useful: the 4 top-level menu entries are not very
useful in the VC context, there's no top level menu for VC operations
and the files not under VC are not shown by default (it would be good
to see them so they can be vc-registered if desired).
It seems to me that a cvs-status like UI would be preferable to
vc-dired.

  reply	other threads:[~2007-07-23 18:18 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 11:42 source repository Paul Pogonyshev
2007-07-03 11:57 ` Jason Rumney
2007-07-03 12:14   ` Paul Pogonyshev
2007-07-03 12:57     ` dhruva
2007-07-03 19:57       ` Karl Fogel
2007-07-04  4:18         ` dhruva
2007-07-03 19:43     ` Eli Zaretskii
2007-07-04  4:26       ` Stephen J. Turnbull
2007-07-04  5:09         ` Nick Roberts
2007-07-04  7:01           ` David Kastrup
2007-07-04  7:14             ` dhruva
2007-07-04  7:33               ` David Kastrup
2007-07-04  9:13           ` Stephen J. Turnbull
2007-07-05  1:30             ` Richard Stallman
2007-07-04 21:22         ` Eli Zaretskii
2007-07-04 21:47           ` David Kastrup
2007-07-05  1:02           ` Stephen J. Turnbull
2007-07-06 15:41         ` merge of multi-tty (was: source repository) Reiner Steib
2007-07-07 16:41           ` Stephen J. Turnbull
2007-07-08 16:56           ` Richard Stallman
2007-07-08 18:57             ` merge of multi-tty Stefan Monnier
2007-07-09 14:29               ` Richard Stallman
2007-07-16 23:41         ` source repository Giorgos Keramidas
2007-07-17  9:15           ` dhruva
2007-07-17 10:29             ` Giorgos Keramidas
2007-07-04  9:54       ` Dan Nicolaescu
2007-07-04 10:11         ` Masatake YAMATO
2007-07-21 17:27           ` vc-dired (was: Re: source repository) Dan Nicolaescu
2007-07-21 18:09             ` vc-dired Masatake YAMATO
2007-08-26  1:51               ` vc-dired Dan Nicolaescu
2007-07-22  3:12             ` vc-dired Stefan Monnier
2007-07-23 18:18               ` Dan Nicolaescu [this message]
2007-07-28  7:06                 ` vc-dired Masatake YAMATO
2007-07-28  8:02                   ` vc-dired David Kastrup
2007-07-28 18:14                     ` vc-dired Masatake YAMATO
2007-07-28 17:09                   ` vc-dired Dan Nicolaescu
2007-07-04  3:43     ` source repository Richard Stallman
2007-07-04  6:52       ` David Kastrup
2007-07-04  7:11       ` Karl Fogel
2007-07-04  7:36         ` Jim Blandy
2007-07-05  1:30         ` Richard Stallman
2007-07-05  3:24           ` Karl Fogel
2007-07-05  6:21             ` Yavor Doganov
2007-07-04  3:43   ` Richard Stallman
2007-07-04  9:57   ` Alan Mackenzie

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=200707231818.l6NIIZe3011091@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=jet@gyve.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.