On 04/11/2018 10:57 AM, Chet Ramey wrote:
> Yep, that's an incompatibility. The `c.c' thing in the original report is
> just a red herring, though.
>
> Chet
>
If you are aiming for compatibility with zsh, the fact that `echo **' recurses
is also a bug.
On 4/11/18 11:51 AM, Murukesh Mohanan wrote:
> Yep, sorry about that, c.c is selected:
>
> $ bash -c '(shopt -s globstar; d=$(mktemp -d); cd "$d"; mkdir a; ln -s a b;
> touch a/a.c c.c; echo **/*.c; cd ..; rm -r "$d")'
> a/a.c b/a.c c.c
>
> Is there a chance of having ** not select symlinks to di
Yep, sorry about that, c.c is selected:
$ bash -c '(shopt -s globstar; d=$(mktemp -d); cd "$d"; mkdir a; ln -s a b;
touch a/a.c c.c; echo **/*.c; cd ..; rm -r "$d")'
a/a.c b/a.c c.c
Is there a chance of having ** not select symlinks to directories, so that
b/c.c doesn't show up in the output?
On
On Wed, Apr 11, 2018 at 06:16:19PM +0300, Ilkka Virta wrote:
> So, given
>
> .
> |-- dir
> | +-- link -> ../otherdir
> +-- otherdir
> +-- subdir
> +-- foo
>
> (that is: mkdir -p dir otherdir/subdir; ln -s ../otherdir dir/link; touch
> otherdir/subdir/foo )
>
> dir/**/foo does not
On 11.4. 17:57, Chet Ramey wrote:
On 4/11/18 10:32 AM, Greg Wooledge wrote:
On Wed, Apr 11, 2018 at 10:21:03AM -0400, Chet Ramey wrote:
On 4/11/18 12:21 AM, Murukesh Mohanan wrote:
This has come up in the past, and was somewhat resolved (<
http://lists.gnu.org/archive/html/bug-bash/2014-03/msg
On 4/11/18 10:32 AM, Greg Wooledge wrote:
> On Wed, Apr 11, 2018 at 10:21:03AM -0400, Chet Ramey wrote:
>> On 4/11/18 12:21 AM, Murukesh Mohanan wrote:
>>> This has come up in the past, and was somewhat resolved (<
>>> http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00097.html>), but
>>> bash
On Wed, Apr 11, 2018 at 10:21:03AM -0400, Chet Ramey wrote:
> On 4/11/18 12:21 AM, Murukesh Mohanan wrote:
> > This has come up in the past, and was somewhat resolved (<
> > http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00097.html>), but
> > bash's behaviour is still a but surprising IMHO.
On 4/11/18 12:21 AM, Murukesh Mohanan wrote:
> This has come up in the past, and was somewhat resolved (<
> http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00097.html>), but
> bash's behaviour is still a but surprising IMHO. While globstar doesn't
> descend further into symlinks, symlinked di
This has come up in the past, and was somewhat resolved (<
http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00097.html>), but
bash's behaviour is still a but surprising IMHO. While globstar doesn't
descend further into symlinks, symlinked directories are selected as a
candidate for matches to
2014-02-04 09:23:21 -0500, Chet Ramey:
> On 1/25/14 6:11 PM, Stephane Chazelas wrote:
> > 2014-01-21 10:19:10 -0500, Chet Ramey:
> > [...]
> >>> I am not so worried about the method used to "fix" globstar -- whether
> >>> we keep backwards compatibility or not -- I am more concerned that we
> >>> h
On 1/25/14 6:11 PM, Stephane Chazelas wrote:
> 2014-01-21 10:19:10 -0500, Chet Ramey:
> [...]
>>> I am not so worried about the method used to "fix" globstar -- whether
>>> we keep backwards compatibility or not -- I am more concerned that we
>>> have at least *some* way of disabling what many peop
2014-01-21 10:19:10 -0500, Chet Ramey:
[...]
> > I am not so worried about the method used to "fix" globstar -- whether
> > we keep backwards compatibility or not -- I am more concerned that we
> > have at least *some* way of disabling what many people view as
> > undesirable behaviour.
>
> It may
On 1/21/14 6:30 AM, Chris Down wrote:
> On Thu, 1 Aug 2013 13:02:31 +0200, Chris Down wrote:
>> As we're probably all aware, `globstar' follows symlinks when doing
>> recursive traversal. Is it possible to, at some future version, have
>> an option that enables/disables (I guess enables by default
On Thu, 1 Aug 2013 13:02:31 +0200, Chris Down wrote:
> As we're probably all aware, `globstar' follows symlinks when doing
> recursive traversal. Is it possible to, at some future version, have
> an option that enables/disables (I guess enables by default for
> backwards compatibility) following sy
As we're probably all aware, `globstar' follows symlinks when doing recursive
traversal. Is it possible to, at some future version, have an option that
enables/disables (I guess enables by default for backwards compatibility)
following symlinks? This can be quite irritating when trying to traverse
15 matches
Mail list logo
