GNU bug report logs - #27844
26.0.50; Dired w/ eshell-ls doesn't support wildcards in file name

Previous Next

Full log

Message #26 received at 27844 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Tino Calancha <tino.calancha <at> gmail.com>
Cc: 27844 <at> debbugs.gnu.org
Subject: Re: bug#27844: 26.0.50; Dired w/ eshell-ls doesn't support wildcards
 in file name
Date: Tue, 01 Aug 2017 18:37:37 +0300

> From: Tino Calancha <tino.calancha <at> gmail.com>
> Date: Tue, 1 Aug 2017 23:06:01 +0900 (JST)
> cc: Tino Calancha <tino.calancha <at> gmail.com>, 27844 <at> debbugs.gnu.org
> 
> > 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.

So we are back to the same issue: this is IMO a user preference, and
you are accustomed to one of the possible behaviors.  And since you
want the behavior to be independent on an already existing user
option, I'm not sure how to proceed.  Maybe you could start by
explaining why you don't want eshell-error-if-no-glob to control this?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.