From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 27844@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#27844: 26.0.50; Dired w/ eshell-ls doesn't support wildcards in file name
Date: Tue, 1 Aug 2017 23:06:01 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1708012258500.27552@calancha-pc> (raw)
In-Reply-To: <8360e71k5p.fsf@gnu.org>
On Tue, 1 Aug 2017, Eli Zaretskii wrote:
> I'm confused: I wasn't commenting on what eshell-extended-glob does, I
> was commenting about your code:
>
> + (let ((matches (eshell-extended-glob file)))
> + (if (consp matches)
> + (mapcar #'file-relative-name matches)
> + (user-error (format "%s: No files matching wildcard" file))))
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> If eshell-extended-glob already signals an error when it's TRT, why do
> you need to signal an error if Eshell doesn't? What am I missing?
I prefer to throw an error because looks familiar compared with
what i see when using GNU/ls.
If i try:
C-x d ~/emacs-master/lisp/*.Z RET
I) with GNU/ls or with ls-lisp:
i get an error and i read in the echo area:
Reading directory: No such file or directory, ~/emacs-master/lisp/*Z
II) with eshell-ls:
I actualy get a Dired buffer with an entry (the directory itself).
I rather prefer if II) behaves as I) regardless on
'eshell-error-if-no-glob', that means, my second patch with the
user-error.
next prev parent reply other threads:[~2017-08-01 14:06 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 [this message]
2017-08-01 15:37 ` Eli Zaretskii
2017-08-01 16:04 ` Tino Calancha
2017-08-01 18:43 ` Eli Zaretskii
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
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.1708012258500.27552@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=27844@debbugs.gnu.org \
--cc=eliz@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).