From: Miles Bader <miles@gnu.org>
Cc: larsh@math.ku.dk, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: dired-move-to-filename-regexp
Date: Mon, 20 Sep 2004 01:00:06 -0400 [thread overview]
Message-ID: <20040920050006.GA7888@fencepost> (raw)
In-Reply-To: <7wr7oxzgs4.fsf@sic.twinsun.com>
On Sun, Sep 19, 2004 at 09:49:15PM -0700, Paul Eggert wrote:
> > If there is a reliable, trouble-free and quick way to check
> > whether the ls program supports --dired, that could be used instead.
>
> Why not have Emacs try "ls -l --dired" first, and, if that doesn't
> work, fall back on "ls -l" without --dired? The --dired usage would
> be considered to "work" only if the output ended in the required
> //DIRED// and //DIRED-OPTIONS// lines in the proper forms.
>
> This procedure should be reliable in practice.
BTW, an annoying thing asbout recent versions of ls with emacs is that when
you rename a file in dired, it calls `ls' with just that file to regenerate
its dired line, but since ls only seems the oneo entry, it shrinks all the
numeric/name fields to their minimum size, so the updated line doesn't match
the rest of the output.
One way this might be fixed would be to have --dired output a "spec" for the
output it generates (e.g., a list of field widths it used), and then also
have an option to ls to use a given "spec" to set the fields widths (which
emacs would then pass in from the previous --dired output).
-Miles
--
Ich bin ein Virus. Mach' mit und kopiere mich in Deine .signature.
next prev parent reply other threads:[~2004-09-20 5:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 7:44 dired-move-to-filename-regexp Lars Hansen
2004-09-19 8:20 ` dired-move-to-filename-regexp Paul Eggert
2004-09-20 0:05 ` dired-move-to-filename-regexp Richard Stallman
2004-09-20 4:49 ` dired-move-to-filename-regexp Paul Eggert
2004-09-20 5:00 ` Miles Bader [this message]
2004-09-21 18:30 ` dired-move-to-filename-regexp Richard Stallman
2004-09-22 6:09 ` dired-move-to-filename-regexp Paul Eggert
2004-09-23 16:45 ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 17:57 ` dired-move-to-filename-regexp Stefan Monnier
2004-09-24 23:40 ` dired-move-to-filename-regexp Richard Stallman
2004-09-25 5:20 ` dired-move-to-filename-regexp Stefan
2004-09-25 15:36 ` dired-move-to-filename-regexp Richard Stallman
2004-09-25 19:08 ` dired-move-to-filename-regexp Stefan
2004-09-26 18:19 ` dired-move-to-filename-regexp Richard Stallman
2004-09-29 3:17 ` dired-move-to-filename-regexp Stefan
2004-09-23 18:27 ` dired-move-to-filename-regexp Paul Eggert
2004-09-24 23:40 ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 23:27 ` dired-move-to-filename-regexp Miles Bader
2004-09-24 23:41 ` dired-move-to-filename-regexp Richard Stallman
2004-09-27 3:34 ` dired-move-to-filename-regexp Miles Bader
2004-09-24 5:51 ` dired-move-to-filename-regexp Jim Meyering
2004-09-25 7:08 ` dired-move-to-filename-regexp Richard Stallman
2004-09-21 18:30 ` dired-move-to-filename-regexp Richard Stallman
2004-09-23 18:59 ` dired-move-to-filename-regexp Lars Hansen
2004-09-24 23:40 ` dired-move-to-filename-regexp Richard Stallman
2004-09-20 6:11 ` dired-move-to-filename-regexp Lars Hansen
2004-09-20 23:28 ` dired-move-to-filename-regexp Paul Eggert
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=20040920050006.GA7888@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsh@math.ku.dk \
--cc=rms@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).