o...@sernet.de wrote:
Description:
After updating to a new distribution with bash version 3.x entglob
does
not work like in bash version 2.x.
Thanks for the report. This problem is specific to pattern substitution
and patterns that begin with `*('. It will be fixed in
Mithu2 wrote:
Hi,
I know in Bash the file completion can be set to provide a menu-list of
possible files. This seems to be the default behaviour. On the other hand,
I could add:
bind 'TAB:menu-complete'
to my .bashrc which allows cycling through the list of completions. But
these
Paul == Paul Jarc p...@po.cwru.edu writes:
Paul Martin Schwenke mar...@meltin.net wrote:
Neither bash.info or bash(1) documents parameter expansion of
the form:
${parameter+word}
Paul It's documented, but it's easy to miss. Just before the
Paul list of
Martin Schwenke wrote:
Paul Jarc writes:
It's documented, but it's easy to miss. Just before the
list of parameter expansion forms is this paragraph:
In each of the cases below, word is subject to tilde
expansion, parameter expansion, command substitution,
and
I wrote a test program test.sh:
trap '
echo this is line 3, but LINENO=$LINENO
' 0
echo this is line 7, and LINENO=$LINENO
---
when I ran it I got
$ sh /tmp/test.sh
this is line 7, and LINENO=7
this is line 3, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to peter360 on 1/9/2009 6:07 PM:
trap '
echo this is line 3, but LINENO=$LINENO
' 0
echo this is line 7, and LINENO=$LINENO
Is this a known problem? Thanks.
In general, LINENO handling is inconsistent among shells. The
