unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Masatake YAMATO <jet@gyve.org>
Cc: emacs-devel@gnu.org
Subject: Re: info inconsistency about "Shell Commands in Dired"
Date: Wed, 25 Aug 2004 13:41:07 +0900 (JST)	[thread overview]
Message-ID: <20040825.134107.52891042.jet@gyve.org> (raw)
In-Reply-To: <200408221946.i7MJkYQ07868@raven.dms.auburn.edu>

> Your environment variable suggestion is not as easy as it appears.
I read all of your message; and agree with you.
I understand the implementation is not so simple.

> First of all, we can not leave things up to the shell.  
As you wrote, what I wanted is we leave things up to the shell.

I think using shell syntax directory is better than adding extra
syntax in dired even if the amount of typing by an user increases.
In some case, avoding mistaking is more impotent than quick operation.

The next example is not so realistic but worth to consider:

    login: root
    Password: *****
    # emacs
    M-x dired 
    Dired (directory): /
    m on some files 
    !
       rm -rf *

If syntax added in dired for * becomes more complex(e.g. putting ''
around *), I'm afraid to use ! in this case.

       rm -rf ${DIRED}

The uesr will feel easier. Especially the uesr ues both the latest emacs
in the CVS repository and older emacs.

Anyway, dired needs new command line parser.  Many objections will be
but I propose remove * and ? from dired and introduce ${dired} and
${DIRED}.

Masatake YAMATO

  reply	other threads:[~2004-08-25  4:41 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 19:08 info inconsistency about "Shell Commands in Dired" Masatake YAMATO
2004-08-21  0:40 ` Luc Teirlinck
2004-08-21  6:38   ` Masatake YAMATO
2004-08-21 20:18     ` Luc Teirlinck
2004-08-22 16:52       ` Richard Stallman
2004-08-21 20:35     ` Luc Teirlinck
2004-08-22  3:55       ` Eli Zaretskii
2004-08-22  4:05         ` Luc Teirlinck
2004-08-21 20:40     ` Luc Teirlinck
2004-08-21 21:24     ` Luc Teirlinck
2004-08-21 10:02   ` Eli Zaretskii
2004-08-21 16:50 ` Richard Stallman
2004-08-21 17:12   ` David Kastrup
2004-08-21 22:49     ` Luc Teirlinck
2004-08-21 23:08       ` Luc Teirlinck
2004-08-21 23:12         ` Luc Teirlinck
2004-08-22  4:17           ` Masatake YAMATO
2004-08-22  7:11             ` David Kastrup
2004-08-22 12:33               ` Masatake YAMATO
2004-08-22 12:59                 ` David Kastrup
2004-08-22 14:00                   ` Masatake YAMATO
2004-08-22 12:43             ` Masatake YAMATO
2004-08-22 15:31               ` Luc Teirlinck
2004-08-22 16:03                 ` Masatake YAMATO
2004-08-22 19:46                   ` Luc Teirlinck
2004-08-25  4:41                     ` Masatake YAMATO [this message]
2004-08-22 15:00             ` Luc Teirlinck
2004-08-22 15:39               ` Masatake YAMATO
2004-08-23 23:26       ` Richard Stallman
2004-08-25 22:36         ` Luc Teirlinck
2004-08-26  4:52           ` Richard Stallman
2004-08-26 21:16             ` Luc Teirlinck
2004-08-27 16:59               ` Richard Stallman
2004-08-27 17:25                 ` David Kastrup
2004-08-27 17:49                   ` Luc Teirlinck
2004-08-28 16:48                   ` Richard Stallman
2004-08-29 20:33                     ` Juri Linkov
2004-08-30 16:05                       ` Richard Stallman
2004-08-25 23:10         ` Luc Teirlinck
2004-08-26  7:28           ` Kim F. Storm
2004-08-26 14:53             ` Luc Teirlinck
2004-08-26 20:53             ` Richard Stallman
2004-08-27  7:21               ` Kim F. Storm
2004-08-28  1:35                 ` Richard Stallman
2004-08-22 16:52     ` 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=20040825.134107.52891042.jet@gyve.org \
    --to=jet@gyve.org \
    --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 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).