bash version: 5.0.2(1)-release
OS: Debian Sid, Linux 4.20.10, x86_64
Tab completion to list the contents of a directory will fail if the
directory includes '[]' in its name.
Example:
$ mkdir foo 'foo[]'; touch foo/baz 'foo[]'/baz
$ ls foo/
Expands to 'foo/baz'
But
$ ls foo\[\]/
Expands
Consider the script at the end of this email. It's effectively
impossible to get or to accept the various values.
Either that or I am doing something incredibly stupid.
(It took me a while to factor this down and try virtually every
workaround that would not involve writing exte
On 2/21/19 10:19 AM, Michael Albinus wrote:
> Chet Ramey writes:
>
>>> PS: Could you pls give me a bug number or something like this, that I
>>> can reference to?
>>
>> You can use the link to the mailing list. There is a more formal bug
>> tracking system on savannah.gnu.org, but few people use
On 2/21/19 6:46 PM, John Van Sickle wrote:
> bash version: 5.0.2(1)-release
> OS: Debian Sid, Linux 4.20.10, x86_64
>
> Tab completion to list the contents of a directory will fail if the
> directory includes '[]' in its name.
Dropped a part from the original patch. Try the attached fix.
Chet
-
Chet Ramey writes:
>> I know. That's why several GNU projects use debbugs.gnu.org, which runs
>> Debian's BTS software.
>
> Few people use that one, either. Most of the active bugs there are at least
> a year old.
???
There are very active projects, with new bugs every single day. I, for
exampl
On 2/22/19 9:49 AM, Michael Albinus wrote:
> Chet Ramey writes:
>
>>> I know. That's why several GNU projects use debbugs.gnu.org, which runs
>>> Debian's BTS software.
>>
>> Few people use that one, either. Most of the active bugs there are at least
>> a year old.
>
> ???
>
> There are very ac
On 2/22/19 6:23 AM, Robert White wrote:
> Consider the script at the end of this email. It's effectively impossible
> to get or to accept the various values.
What are "the various values"?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa,
On Fri, Feb 22, 2019 at 3:24 AM Robert White wrote:
(...)
> tail --lines=+3 /proc/partitions | grep -v ram |
> while read -a RECORD
> do
(...)
> eval [${INLINE[UUID]}]=boo
(...)
> done
>
> echo " Keys: " "${![@]}" = "${[@]}"
> echo " Keys: " "${![@]}" = "${[@]}"
>
On 2/22/19 4:17 PM, Eduardo Bustamante wrote:
On Fri, Feb 22, 2019 at 3:24 AM Robert White wrote:
(...)
tail --lines=+3 /proc/partitions | grep -v ram |
while read -a RECORD
do
(...)
eval [${INLINE[UUID]}]=boo
(...)
done
echo " Keys: " "${![@]}" = "${[@]}"
echo "
On Sat, Feb 23, 2019 at 01:48:08AM +, Robert White wrote:
(...)
> Your syntax checker is straight tripping on that SC1036 error dude. Array
> assignment using ARRAYNAME=( expression ) is completely legal and correct
> with or without the eval. The structure even allows for line continuation
> j
10 matches
Mail list logo
