unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: dired without -l, wdired fails
Date: Tue, 16 Feb 2010 17:17:58 +1100	[thread overview]
Message-ID: <87635x7lgp.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.1279.1266241033.14305.help-gnu-emacs@gnu.org

Andreas Roehler <andreas.roehler@online.de> writes:

> Tassilo Horn wrote:
>> Andreas Roehler <andreas.roehler@online.de> writes:
>> 
>
> IIRC `dired' basically displays the output of
> shell-command `ls [options]' in a buffer, afterwards working
> with, send it back to the shell.
>
> From this I never understood this limitation, which looks
> inconvenient in many respects.
>
Noting of course taht there is also a lisp version of 'ls', which
provides this functionality on non-unix like platforms and provides some
additional functionality on platforms that do have a shell based 'ls'. 

My guess is that by forcing the -l switch, you get a fairly standard and
easy to parse output, making the code easier to maintain. Without -l,
you have to have more code to handle the parsing of the output and
possibly even more problematic, more code to handle the display and
movement within that display etc. 

Tim



-- 
tcross (at) rapttech dot com dot au


  parent reply	other threads:[~2010-02-16  6:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-15 12:55 dired without -l, wdired fails Andreas Roehler
2010-02-15 13:10 ` Tassilo Horn
2010-02-15 13:38   ` Andreas Roehler
2010-02-15 14:43     ` Tassilo Horn
     [not found]   ` <mailman.1279.1266241033.14305.help-gnu-emacs@gnu.org>
2010-02-16  6:17     ` Tim X [this message]
2010-02-16 10:41       ` Andreas Röhler
2010-02-17 10:48         ` Bernardo
2010-02-17 12:15           ` Andreas Röhler
     [not found]           ` <mailman.1388.1266408803.14305.help-gnu-emacs@gnu.org>
2010-02-17 15:01             ` Stefan Monnier
2010-02-17 18:03               ` Andreas Röhler
     [not found]               ` <mailman.1399.1266429708.14305.help-gnu-emacs@gnu.org>
2010-02-17 19:41                 ` Stefan Monnier
2010-02-17 20:50                   ` Andreas Röhler
2010-02-17 21:58                     ` Tassilo Horn
2010-02-18  8:05                       ` Andreas Röhler
2010-02-17 21:36               ` Tim X
2010-02-18  7:57                 ` Andreas Röhler
2010-02-18  9:32                   ` Peter Dyballa
2010-02-18 13:48                   ` Stefan Monnier
2010-02-19  9:12                     ` Andreas Röhler
     [not found]       ` <mailman.1323.1266316798.14305.help-gnu-emacs@gnu.org>
2010-02-16 14:28         ` Stefan Monnier
2010-02-16 17:57           ` Andreas Röhler
2010-02-16 23:01             ` Stefan Monnier
2010-02-17  8:42               ` Andreas Röhler
     [not found]             ` <mailman.1361.1266361317.14305.help-gnu-emacs@gnu.org>
2010-02-17  6:34               ` Tim X
     [not found] <mailman.1277.1266238414.14305.help-gnu-emacs@gnu.org>
2010-02-16  6:01 ` Tim X

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=87635x7lgp.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@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.
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).