oh i see, thank you big time for pointing it out so good
:))
On Mon, Mar 1, 2021 at 11:22 AM felix wrote:
> On Sun, Feb 28, 2021 at 10:32:13PM +, k...@plushkava.net wrote:
> > Why not indeed. However, I think that I'm able to decipher this.
> >
> > $ declare -A map; key=$'foo\34bar';
On Sun, Feb 28, 2021 at 10:32:13PM +, k...@plushkava.net wrote:
> Why not indeed. However, I think that I'm able to decipher this.
>
> $ declare -A map; key=$'foo\34bar'; map[$key]=
> $ set -x
> $ : "$key"
> + : $'foo\034bar'
> $ unset "map[$key]"
> + unset 'map[foobar]'
>
> For the unset
it just displays the wrong data completly, the special chars cutted off, ..
..
On Mon, Mar 1, 2021 at 10:28 AM Alex fxmbsw7 Ratchev
wrote:
> i still dont understand, ( you speak more special english than code ), why
> unset wont display the special chars, but then i suppose its not much of a
>
i still dont understand, ( you speak more special english than code ), why
unset wont display the special chars, but then i suppose its not much of a
bug .. ?
On Mon, Mar 1, 2021 at 1:19 AM Chet Ramey wrote:
> On 2/28/21 6:19 PM, k...@plushkava.net wrote:
>
> >> The check for shell special
On 2/28/21 6:19 PM, k...@plushkava.net wrote:
The check for shell special characters, which results in single quoting,
comes before whether there are any characters that would require ANSI-C
quoting. This is not specific to unset.
In fairness, I don't think it's strictly incorrect to say that
On 28/02/2021 22:47, Chet Ramey wrote:
On 2/28/21 5:32 PM, k...@plushkava.net wrote:
On 28/02/2021 22:13, Chet Ramey wrote:
On 2/27/21 6:14 AM, Alex fxmbsw7 Ratchev wrote:
but they get unset right, just doesnt display em
i have stuff with $'\34' separator and in set -x output the text is
On 2/28/21 5:32 PM, k...@plushkava.net wrote:
On 28/02/2021 22:13, Chet Ramey wrote:
On 2/27/21 6:14 AM, Alex fxmbsw7 Ratchev wrote:
but they get unset right, just doesnt display em
i have stuff with $'\34' separator and in set -x output the text is just
flat for the unset
+ unset
On 28/02/2021 22:13, Chet Ramey wrote:
On 2/27/21 6:14 AM, Alex fxmbsw7 Ratchev wrote:
but they get unset right, just doesnt display em
i have stuff with $'\34' separator and in set -x output the text is just
flat for the unset
+ unset 'dat[kwmetest]' 'dat[1kw1]' 'dat[1take]' 'dat[1code]'
On 2021/02/28 14:13, Chet Ramey wrote:
On 2/27/21 6:14 AM, Alex fxmbsw7 Ratchev wrote:
These code fragments have nothing to do with each other. Why not include
a self-contained example that includes relevant `stuff' in what you're
passing to `unset'?
cuz he's trollin us?
On 2/27/21 6:14 AM, Alex fxmbsw7 Ratchev wrote:
but they get unset right, just doesnt display em
i have stuff with $'\34' separator and in set -x output the text is just
flat for the unset
+ unset 'dat[kwmetest]' 'dat[1kw1]' 'dat[1take]' 'dat[1code]'
code includes
but they get unset right, just doesnt display em
i have stuff with $'\34' separator and in set -x output the text is just
flat for the unset
+ unset 'dat[kwmetest]' 'dat[1kw1]' 'dat[1take]' 'dat[1code]'
code includes
minuskws_p1=$nspace$SUBSEP$minuskws_id$SUBSEP \
11 matches
Mail list logo
