Hi Uwe,
On 2014-03-12 21:37, Uwe Storbeck wrote:
A few corrections to my last mail:
bash completion before the first letter of the file name fails at
all, even for "normal" file names:
$ mkdir /tmp/test && cd /tmp/test && touch a
$ ls
Also not all characters where the completion after
On 3/12/14 12:14 PM, Evan Gates wrote:
> setup:
> foo() { printf "%q\n" "$IFS" >&2; printf "%s\n" "$*" >&2; }
> IFS=: read <<< "$(foo bar baz qux)"
>
> bash 4.2 output:
> :
> bar:baz:qux
>
> bash 4.3 output:
> :
> bar baz qux
>
>
> IFS is still set within the function call, but isn't being used
setup:
foo() { printf "%q\n" "$IFS" >&2; printf "%s\n" "$*" >&2; }
IFS=: read <<< "$(foo bar baz qux)"
bash 4.2 output:
:
bar:baz:qux
bash 4.3 output:
:
bar baz qux
IFS is still set within the function call, but isn't being used in the
expansion of "$*"
-emg
Package: bash
Version: 4.3-2
Severity: minor
X-Debbugs-Cc: bug-bash@gnu.org
According to the manual, either the function keyword or parentheses should be
sufficient to define a function:
Shell Function Definitions
A shell function is an object that is called like a simple command and
execu
