On Sun, Mar 06, 2016 at 10:16:58PM +, Stephane Chazelas wrote:
> Today, I realised that GLOBIGNORE doesn't work at all like ksh's
> FIGNORE.
>
> With
>
> GLOBIGNORE=x*
>
> we're not filtering out files whose *name* starts with "x" from
> globs but those whose *path* starts with "x".
>
> In
Today, I realised that GLOBIGNORE doesn't work at all like ksh's
FIGNORE.
With
GLOBIGNORE=x*
we're not filtering out files whose *name* starts with "x" from
globs but those whose *path* starts with "x".
In
echo *
files whose name starts with "x" will be excluded, but not in
echo ./*
I think
Please reply to the list and not just me. There are a lot of helpful people
out there. Perhaps a "reply all"?
On Sun, Mar 6, 2016 at 5:26 PM, Val Krem wrote:
> Hi John,
> Thank you very much!
> I chose to put it as a function in my .bashrc.
> what happened is that
> if I dot give the the two ar
2016-03-06 22:16:58 +, Stephane Chazelas:
[...]
> $ bash -c 'GLOBIGNORE=x*; echo .*'
> .*
> $ bash -c 'GLOBIGNORE=x*; echo ./.*'
> ./. ./..
> $ bash -c 'GLOBIGNORE=x*; echo .*/a'
> ./a ../a
>
> To truely exclude . and .., one needs:
>
> shopt -s extglob
> GLOBIGNORE='?(*/)@(.|..)'
[...]
That
On 3/5/16 5:05 AM, Chris Staub wrote:
> When building Bash 4.4-rc1 with "make -j4", it is possible to get a make
> error due to the build system attempting to copy a file to a directory
> before that directory has been created. It will try to copy "Makefile.inc"
> to $(loadablesdir), but the comman
