From: Leo <sdl.web@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Feature request: dired-open-marked-files
Date: Sun, 15 Mar 2009 11:25:01 +0000 [thread overview]
Message-ID: <xbaifxhfqb8y.fsf@cam.ac.uk> (raw)
In-Reply-To: 003a01c9a542$5a95c880$0200a8c0@us.oracle.com
On 2009-03-15 07:47 +0000, Drew Adams wrote:
>> I've not examined them all in detail; let's just say that some of
>> them seem obviously useful and not dangerous, e.g., `dired-jump' and
>> `dired-do-find-marked-files' (I've seen the latter functionality
>> requested several times recently on #emacs), whereas others seem less
>> useful, and maybe don't merit a keybinding by default (e.g.,
>> `dired-man'). `dired-vm-read-only-folders' probably shouldn't be
>> there, as VM isn't distributed with emacs or really all that commonly
>> used (and for a long time, didn't even officially support
>> non-xemacs).
I can see and agree with Miles's point. If the maintainer of dired can
be brought on board and a few people (that understand dired well) can
work out a plan off line as a first step to re-organise dired code, we
might be able to make a move on this.
It often happens in Emacs that tons of people are voicing their opinions
and nothing gets done in the end. I remember once RMS agreed to bring
some functions from cl.el to emacs core, which is a window of
opportunity missed.
>> But I generally agree with you. At the least, the split into dired
>> and dired-x seems arbitrary and deserves re-examination.
--
.: Leo :. [ sdl.web AT gmail.com ] .: I use Emacs :.
www.git-scm.com
git - the one true version control system
next prev parent reply other threads:[~2009-03-15 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 1:26 Feature request: dired-open-marked-files Vivek Dasmohapatra
2009-03-15 6:39 ` Drew Adams
2009-03-15 6:44 ` Miles Bader
2009-03-15 7:03 ` Drew Adams
2009-03-15 7:15 ` Miles Bader
2009-03-15 7:47 ` Drew Adams
2009-03-15 11:25 ` Leo [this message]
2009-03-16 9:42 ` Richard M Stallman
2009-03-15 15:08 ` Vivek Dasmohapatra
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=xbaifxhfqb8y.fsf@cam.ac.uk \
--to=sdl.web@gmail.com \
--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 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.