Ian Kelling wrote:
I'm not sure your reading it quite right. Chet gets it.
Another way of explaining it is:
dotglob does not affect the files "." and "..".
---
After I saw Chet's response, I sorta got you were referring to the
"exceptions". Thanks.
-l
On Tue, Sep 27, 2016, at 11:08 AM, Chet Ramey wrote:
>
> Thanks for the report. There should be something in there about `.'
> and `..' always having to be matched explicitly.
Yw. I noticed another improvement that could be made to the
docs. How do you prefer patches? And, I assume you manually
On Tue, Sep 27, 2016, at 09:41 AM, L. A. Walsh wrote:
>
>
> Ian Kelling wrote:
> > The docs currently say:
> >
> > "When a pattern is used for filename expansion, the character '.' at
> > the start of a filename or immediately following a slash must be matched
> > explicitly, unless the shell opt
On 9/26/16 6:40 PM, Ian Kelling wrote:
> The docs currently say:
>
> "When a pattern is used for filename expansion, the character '.' at
> the start of a filename or immediately following a slash must be matched
> explicitly, unless the shell option 'dotglob' is set.
>
> The last bit should be
Ian Kelling wrote:
The docs currently say:
"When a pattern is used for filename expansion, the character '.' at
the start of a filename or immediately following a slash must be matched
explicitly, unless the shell option 'dotglob' is set.
The last bit should be changed to say
unless the sh
The docs currently say:
"When a pattern is used for filename expansion, the character '.' at
the start of a filename or immediately following a slash must be matched
explicitly, unless the shell option 'dotglob' is set.
The last bit should be changed to say
unless the shell option 'dotglob' is
