From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 27844@debbugs.gnu.org
Subject: bug#27844: 26.0.50; Dired w/ eshell-ls doesn't support wildcards in file name
Date: Tue, 01 Aug 2017 21:43:41 +0300 [thread overview]
Message-ID: <83tw1ryvqa.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1708020050590.14099@calancha-pc> (message from Tino Calancha on Wed, 2 Aug 2017 01:04:20 +0900 (JST))
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Wed, 2 Aug 2017 01:04:20 +0900 (JST)
> cc: Tino Calancha <tino.calancha@gmail.com>, 27844@debbugs.gnu.org
>
> 1) I am imaging one user in a system without an external 'ls' installed.
>
> 2) This hypothetical user wants to use Dired; after searching the web,
> find s?he could do it via eshell.
>
> 3) I assume this user is not interested in the eshell internals: just want
> to have Dired running without complications. That means
> 'eshell-error-if-no-glob' keeps its default, nil.
How about binding eshell-error-if-no-glob to non-nil when eshell/ls is
called from Dired, then?
> I like the idea that Dired behaves uniformsly regardless on if we are
> using an external 'ls' or an elisp emulation of it.
That's an unreachable ideal, because there are too many versions of
'ls' out there. GNU 'ls' is just one of them. And sometimes the
error comes from the shell which expands wildcards, not from 'ls'
itself.
next prev parent reply other threads:[~2017-08-01 18:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 3:27 bug#27844: 26.0.50; Dired w/ eshell-ls doesn't support wildcards in file name Tino Calancha
2017-07-27 9:23 ` Tino Calancha
2017-07-29 9:06 ` Eli Zaretskii
2017-08-01 3:00 ` Tino Calancha
2017-08-01 13:40 ` Eli Zaretskii
2017-08-01 14:06 ` Tino Calancha
2017-08-01 15:37 ` Eli Zaretskii
2017-08-01 16:04 ` Tino Calancha
2017-08-01 18:43 ` Eli Zaretskii [this message]
2017-08-02 8:49 ` Tino Calancha
2017-08-04 13:15 ` Eli Zaretskii
2017-07-29 9:05 ` Eli Zaretskii
2017-08-06 4:30 ` Tino Calancha
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=83tw1ryvqa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27844@debbugs.gnu.org \
--cc=tino.calancha@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.