unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <tino.calancha@gmail.com>
To: John Wiegley <jwiegley@gmail.com>
Cc: 27919@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#27919: 25.2.50; dired + eshell-ls: fallback to external ls fails
Date: Fri, 4 Aug 2017 17:34:35 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1708041731030.11885@calancha-pc> (raw)
In-Reply-To: <m2y3r02uld.fsf@newartisans.com>



On Thu, 3 Aug 2017, John Wiegley wrote:

>>>>>> Glenn Morris <rgm@gnu.org> writes:
>
>> Why is it desirable to use eshell ls with dired instead of ls-lisp? Maybe it
>> would be better to remove it rather than fix it. (It usually goes well when
>> I suggest this...)
>
> I like it more than ls-lisp, and it pays attention to all the same options you
> can use to configure eshell/ls at the Eshell command-line.  If anything, why
> not get rid of ls-lisp?
I think 'The battle of emulated ls with elisp' is about to start.  I read
about in a Tolkien book; don't remember who won, though.





  parent reply	other threads:[~2017-08-04  8:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 15:59 bug#27919: 25.2.50; dired + eshell-ls: fallback to external ls fails Tino Calancha
2017-08-02 19:06 ` John Wiegley
2017-08-03  3:16   ` Tino Calancha
2017-08-03 18:47     ` John Wiegley
2017-08-03 21:35       ` Glenn Morris
2017-08-03 21:46         ` John Wiegley
2017-08-04  6:04           ` Eli Zaretskii
2017-08-04 17:05             ` John Wiegley
2017-08-04 17:23               ` Eli Zaretskii
     [not found]               ` <<83shh7w8le.fsf@gnu.org>
2017-08-04 17:37                 ` Drew Adams
2017-08-04  8:34           ` Tino Calancha [this message]
2022-02-10  7:59 ` Lars Ingebrigtsen
     [not found] <<87lgn2vu3g.fsf@calancha-pc>

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=alpine.DEB.2.20.1708041731030.11885@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=27919@debbugs.gnu.org \
    --cc=jwiegley@gmail.com \
    /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).