From: Richard Stallman <rms@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: esr@thyrsus.com, esr@snark.thyrsus.com, emacs-devel@gnu.org,
monnier@iro.umontreal.ca, harsanyi@mac.com
Subject: Re: Introducing 'unrecognized and 'ignored
Date: Sat, 05 Jan 2008 00:54:12 -0500 [thread overview]
Message-ID: <E1JB1z2-00062N-94@fencepost.gnu.org> (raw)
In-Reply-To: <200801031805.m03I5SBf022748@oogie-boogie.ics.uci.edu> (message from Dan Nicolaescu on Thu, 03 Jan 2008 10:05:25 -0800)
The disadvantages or using dired:
Several of these are not persuasive (at least based on what
you've said so far).
- performance -- the difference is HUGE
What is the connection between using dired and this slowdown?
- clutter - dired has 4 top level menus that are mostly useless in the
VC context
That is not a real problem.
It is easy for a variant of Dired to override them.
- availability of simple key bindings: dired takes most single key
bindings, forcing vc-dired to use the "v" prefix
That is not a real problem. vc-dired could rebind some Dired keys,
and still preserve most of the advantage of commonality with Dired.
- future extensibility - VC systems are evolving at a fast pace
nowadays, being able to easily make changes to accommodate new
features is very important.
I see no point paying the price today for a benefit that may only
possibly develop. I'd rather pay that price if and when there is a
real benefit to be gained. It won't be more work then than it is
today.
On the other hand, this could be a significant reason:
- display flexibility -- it is much easier to do custom displays as
needed by VC using ewocs than to retrofit it into dired. Just look
at the PCL-CVS display and compare it with vc-dired.
If custom displays are needed, that probably requires splitting off.
Are custom displays needed? What would you want to use them for?
next prev parent reply other threads:[~2008-01-05 5:54 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 17:45 Introducing 'unrecognized and 'ignored Eric S. Raymond
2007-12-28 23:01 ` Dan Nicolaescu
2007-12-29 2:48 ` Alexandru Harsanyi
2007-12-29 11:45 ` Eric S. Raymond
2008-01-02 2:02 ` Stefan Monnier
2008-01-02 2:19 ` Eric S. Raymond
2008-01-02 4:16 ` Stefan Monnier
2008-01-02 4:45 ` Dan Nicolaescu
2008-01-02 11:50 ` Eric S. Raymond
2008-01-02 17:31 ` Dan Nicolaescu
2008-01-03 9:50 ` Richard Stallman
2008-01-03 18:05 ` Dan Nicolaescu
2008-01-03 18:19 ` Eric S. Raymond
2008-01-05 5:54 ` Richard Stallman [this message]
2008-01-05 9:01 ` Dan Nicolaescu
2008-01-05 14:34 ` Eric S. Raymond
2008-01-05 22:25 ` Stefan Monnier
2008-01-06 10:37 ` Dan Nicolaescu
2008-01-06 15:57 ` Eric S. Raymond
2008-01-18 23:31 ` Dan Nicolaescu
2008-01-06 20:00 ` Tom Tromey
2008-01-06 21:03 ` Stefan Monnier
2008-01-07 2:59 ` Dan Nicolaescu
2008-01-07 3:26 ` Eric S. Raymond
2008-01-07 3:36 ` Dan Nicolaescu
2008-01-07 3:59 ` Stefan Monnier
2008-01-07 12:56 ` Eric S. Raymond
2008-01-07 15:31 ` Stefan Monnier
2008-01-07 11:30 ` Richard Stallman
2008-01-07 12:54 ` Eric S. Raymond
2008-01-07 15:32 ` Stefan Monnier
2008-01-08 19:06 ` Richard Stallman
2008-01-08 19:34 ` Miles Bader
2008-01-07 3:22 ` Dan Nicolaescu
2008-01-07 3:03 ` Tom Tromey
2008-01-07 4:01 ` Stefan Monnier
2008-01-07 21:15 ` PCL-CVS buffers (was: Introducing 'unrecognized and 'ignored) Reiner Steib
2008-01-08 2:33 ` PCL-CVS buffers Stefan Monnier
2008-01-18 23:46 ` Introducing 'unrecognized and 'ignored Dan Nicolaescu
2008-01-19 0:10 ` Tom Tromey
2008-01-19 1:20 ` Dan Nicolaescu
2008-01-19 6:00 ` Tom Tromey
2008-01-19 17:05 ` Dan Nicolaescu
2008-01-19 19:40 ` Stefan Monnier
2008-01-19 21:01 ` Thien-Thi Nguyen
2008-01-20 17:18 ` Dan Nicolaescu
2008-01-20 20:24 ` Thien-Thi Nguyen
2008-01-20 17:08 ` Dan Nicolaescu
2008-01-20 19:08 ` Tom Tromey
2008-01-20 20:14 ` Stefan Monnier
2008-01-20 19:45 ` Tom Tromey
2008-01-22 1:35 ` Dan Nicolaescu
2008-01-19 20:03 ` Thien-Thi Nguyen
2008-01-20 19:24 ` Stefan Monnier
2008-01-20 20:30 ` Thien-Thi Nguyen
2008-01-21 15:18 ` Stefan Monnier
2008-01-21 15:30 ` Dan Nicolaescu
2008-01-21 15:56 ` Stefan Monnier
2008-01-21 15:34 ` Thien-Thi Nguyen
2008-01-06 8:09 ` Richard Stallman
2008-01-02 11:46 ` Eric S. Raymond
2008-01-02 20:38 ` Stefan Monnier
2008-01-02 22:11 ` Eric S. Raymond
2008-01-02 23:06 ` Stefan Monnier
2008-01-02 23:29 ` Eric S. Raymond
2008-01-03 14:30 ` Stefan Monnier
2008-01-03 17:41 ` Eric S. Raymond
2008-01-05 5:54 ` Richard Stallman
2008-01-02 23:13 ` Dan Nicolaescu
2008-01-02 23:33 ` Eric S. Raymond
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=E1JB1z2-00062N-94@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=harsanyi@mac.com \
--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).