From: David Kastrup <dak@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: dieter@duenenhof-wilhelm.de, rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: dired mode recursive delete
Date: Mon, 04 Jun 2007 07:21:11 +0200 [thread overview]
Message-ID: <86y7j047nc.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <87r6os8w31.fsf@jurta.org> (Juri Linkov's message of "Mon\, 04 Jun 2007 01\:59\:46 +0300")
Juri Linkov <juri@jurta.org> writes:
>>> But advantages of using external commands are numerous: they are
>>> rich of features whose reimplementation in Emacs doesn't sound
>>> reasonable.
>>
>> What use are numerous features in external commands when there is no
>> interface from Emacs to them?
>>
>> I can call external programs as much as I like for solving some
>> Emacs-internal task, but the number of options that I am not going to
>> use is not relevant at all.
>
> Designing a good interface for using them is a good goal. For example,
> I imagine that just like some dired commands, when invoked with the prefix
> key, ask for the command switches (`C-u =' asks for diff switches and `C-u s'
> asks for ls switches), in the same way `C-u C' and `C-u R' could ask
> for cp and mv switches and call these commands.
But Emacs can't use external commands for moving and copying non-local
files, anyway, so there is no point in asking for command line options
which Emacs itself does not understand when Emacs will likely not be
able to use a command line.
--
David Kastrup
next prev parent reply other threads:[~2007-06-04 5:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 17:36 dired mode recursive delete Neal Becker
2007-05-30 17:59 ` Stephen Berman
2007-05-30 18:11 ` David Kastrup
2007-05-31 22:31 ` Richard Stallman
2007-06-01 5:03 ` David Kastrup
2007-06-01 5:33 ` Romain Francoise
2007-06-01 5:35 ` Romain Francoise
2007-06-02 23:28 ` Juri Linkov
2007-06-03 5:02 ` David Kastrup
2007-06-03 9:29 ` Juri Linkov
2007-06-03 10:34 ` Dieter Wilhelm
2007-06-03 12:09 ` Juri Linkov
2007-06-03 13:09 ` martin rudalics
2007-06-03 18:43 ` Juri Linkov
2007-06-03 20:57 ` Eli Zaretskii
2007-06-03 21:28 ` Juri Linkov
2007-06-03 21:57 ` David Kastrup
2007-06-03 22:59 ` Juri Linkov
2007-06-04 5:21 ` David Kastrup [this message]
2007-06-04 23:54 ` Juri Linkov
2007-06-03 19:46 ` David Kastrup
2007-06-03 20:00 ` Juri Linkov
2007-06-03 20:20 ` David Kastrup
2007-06-03 20:31 ` Juri Linkov
2007-06-04 21:22 ` Dieter Wilhelm
2007-06-03 19:55 ` Giorgos Keramidas
2007-06-03 20:14 ` Juri Linkov
2007-06-01 17:54 ` Richard Stallman
2007-06-03 18:42 ` Juri Linkov
2007-06-02 16:02 ` Kevin Rodgers
2007-06-02 19:13 ` David Kastrup
2007-06-13 7:53 ` Kevin Rodgers
2007-06-13 8:03 ` David Kastrup
2007-06-13 8:17 ` Stephen Leake
2007-06-13 8:26 ` David Kastrup
2007-06-03 21:26 ` Richard Stallman
2007-06-13 8:11 ` Kevin Rodgers
2007-05-31 22:31 ` Richard Stallman
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=86y7j047nc.fsf@lola.quinscape.zz \
--to=dak@gnu.org \
--cc=dieter@duenenhof-wilhelm.de \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rudalics@gmx.at \
/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).