shopt -s localvar_inherit
declare -A var
f() { declare var+=([0]=X); }; f
Segmentation fault: 11
* thread #1, stop reason = signal SIGSTOP
* frame #0: 0x000107abb72f bash`hash_search + 47
frame #1: 0x000107ac7324 bash`assoc_insert + 36
frame #2: 0x000107ac6658 bash`assign_co
In the latest devel this issue is fixed for the case that the local nameref
points to a non-existent variable but there is still a bug if the variable
pointed to by a local nameref already exists. In such a case, `declare'
commands after the initial `declare -n' end up modifying the value and/or
a
On 7/25/18 12:34 PM, Michal Pesa wrote:
> Would it also be possible to add documentation for the characters denoting
> a file’s typein "visible-stats"?
They're basically the standard characters that `ls' has used forever.
If you'd like to submit a patch, I'll take a look at it.
Chet
--
``The ly
It would be obvious then what color exactly needs to be change in the
LS_COLORS variable if a different color was desired.
On 7/25/2018 8:44 PM, Chet Ramey wrote:
On 7/24/18 5:16 PM, Michal Pesa wrote:
Hello,
documentation for the readline variable "colored-completion-prefix" doesn't
state wh
On 7/24/18 5:16 PM, Michal Pesa wrote:
> Hello,
> documentation for the readline variable "colored-completion-prefix" doesn't
> state which part of the "LS_COLORS" is used.
Does it need to? I don't see that adding anything to the user experience.
The only real need is to specify that if LS_COLORS
Would it also be possible to add documentation for the characters
denoting a file’s typein "visible-stats"?
On 7/24/2018 11:16 PM, Michal Pesa wrote:
Hello,
documentation for the readline variable "colored-completion-prefix"
doesn't state which part of the "LS_COLORS" is used.
Thank you for
