all messages for Emacs-related lists mirrored at yhetil.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: Thu, 3 Aug 2017 12:16:50 +0900 (JST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1708031207010.2229@calancha-pc> (raw)
In-Reply-To: <m2tw1pzt5k.fsf@newartisans.com>



On Wed, 2 Aug 2017, John Wiegley wrote:

>>>>>> "TC" == Tino Calancha <tino.calancha@gmail.com> writes:
>
> TC> M-: (dired source-directory "-lg") RET
> TC> ;; Signal eshell-interactive-output-p: (wrong-type-argument arrayp nil)
>
> Why would eshell be involving with using dired at all?  Do you have a
> customization present that is causing this?
Not me.  I am just testing all the functionality available.
Someone added in 2000 a defcustom `eshell-ls-use-in-dired', so 
that you can run eshell-ls to list directories with Dired.

Now i understand why i get this error: the dired support was added
'a posteriori'.

I think an user who want to set `eshell-ls-use-in-dired' non-nil is
likely someone with no external 'ls' installed.





  reply	other threads:[~2017-08-03  3:16 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 [this message]
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
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

* 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.1708031207010.2229@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.