Is this correct?
declare -A l1
l1=([a]=b [c]=d)
echo ${!l1[@]}
l1=($(echo [a]=b [c]=d))
echo ${!l1[@]}
$ bash t4
c a
[a]=b [c]=d
If so, why? And how can I assign a list of members to an associative array?
Please disregard that ... there's something there, but I haven't
distilled it yet.
On 5/4/22 9:06 AM, n952162 wrote:
In vi mode
if you enter, .e.g. 2f) (put the cursur on the second following
occurance of a right paren), it works, I think, "virtually", but the
displayed
In vi mode
if you enter, .e.g. 2f) (put the cursur on the second following
occurance of a right paren), it works, I think, "virtually", but the
displayed line is all garbled. You can keep editting and create a
correct command, but only blindly.
On 2/7/21 6:04 PM, Chet Ramey wrote:
On 2/7/21 11:51 AM, n952162 wrote:
Hi,
I use this string as my prompt:
$?${boldon}$UCODE\w${boldoff}>
where boldon and boldoff are gotten from "tput smso" and "tput rmso".
Works fine on my x86_64 boxes at 5.0.18(1) but on my r
Hi,
I use this string as my prompt:
$?${boldon}$UCODE\w${boldoff}>
where boldon and boldoff are gotten from "tput smso" and "tput rmso".
Works fine on my x86_64 boxes at 5.0.18(1) but on my raspberry-pi, at
5.0.3(1), I need to use \[ and \].
Am I not seeing something?
On 1/13/21 6:00 PM, bug-bash-requ...@gnu.org wrote:
and then (inevitably)
simply reports an error, because its such files aren't executable.
But it is not inevitable. Using 'cp' as an example. Assuming
you have /usr/bin in your PATH, but ~/bin is in your PATH before
/usr/bin, then try:
"tou
harset="ISO-8859-15"
On 2021-01-10 at 08:52 +0100, n952162 wrote:
Hello,
I consider it a bug that bash (and its hash functionality) includes
non-executable files in its execution look-up and then (inevitably)
simply reports an error, because its such files aren't executable.
Hello,
I consider it a bug that bash (and its hash functionality) includes
non-executable files in its execution look-up and then (inevitably)
simply reports an error, because its such files aren't executable.
Perhaps it's there to support PATH look up for arguments to the bash
command. That w
