> On Jul 27, 2020, at 4:02 AM, Andreas Schwab wrote:
>
> On Jul 27 2020, Lawrence Velázquez wrote:
>
>> If word splitting were not performed in compound assignments, this...
>>
>>foo=(a b c)
>>
>> ...would not work.
>
> This is not true. Field splitting is only relevant for words generat
On 7/25/20 12:21 PM, Daniel Molina wrote:
> Hi,
>
> I found some aspects of readline documentation that seem inconsistent to
> me and I wanted to share them.
>
> 1. The difference between backward-kill-line and unix-line-discard
> readline commands.
>
> Documentation states:
>
> backward
On 7/24/20 7:44 PM, Grisha Levit wrote:
> The value of `histexpand' is not reset when executing a shebang-less
> script. (Admittedly, this is unlikely to matter since the value of
> `history' *is* properly reset.)
>
> $ cat > /tmp/test1.sh <<"EOF"
> #!/usr/bin/env bash
> echo $-
> EOF
> $ cat > /t
On 7/24/20 2:25 AM, Grisha Levit wrote:
> Having IGNOREEOF defined prior to invoking a function that uses `local -'
> causes IGNOREEOF to be set to `10' after the function returns.
>
> $ IGNOREEOF=0; f() { local -; }; f; echo $IGNOREEOF
> 10
Yes, that's the default. `local -' saves the st
On 7/24/20 2:14 AM, Grisha Levit wrote:
> The value of $SHELLOPTS is not always updated correctly after returning
> from a function that modifies options after using `local -'.
Thanks for the report. I think this is an easy fix.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chauce
On 7/24/20 1:32 AM, Grisha Levit wrote:
> It seems that disabling the EOF character does not have an effect on
> readline.
No. Readline will bind a few of the special tty characters to their
readline equivalents (controlled by the `bind-tty-special-chars' variable),
but the EOF character is not o
On Mon, Jul 27, 2020 at 01:31:32AM -0400, Dale R. Worley wrote:
> So it seems like the word splitting in "A=(X$Z)" is incorrect.
If the documentation doesn't support word splitting in that case,
then it's the documentation that will need to change, not the shell.
Word splitting in that context is
27 Temmuz 2020 Pazartesi tarihinde Alexey Izbyshev
yazdı:
> On 2020-07-27 10:06, Lawrence Velázquez wrote:
>
>> On Jul 27, 2020, at 1:31 AM, Dale R. Worley wrote:
>>> Interesting. The documentation for 4.2.53(1) says this about parameter
>>> assignments generally, with no special rules for comp
On Jul 27 2020, Lawrence Velázquez wrote:
> If word splitting were not performed in compound assignments, this...
>
> foo=(a b c)
>
> ...would not work.
This is not true. Field splitting is only relevant for words generated
by other expansions, not for literal tokens.
Andreas.
--
Andreas
On 2020-07-27 10:06, Lawrence Velázquez wrote:
On Jul 27, 2020, at 1:31 AM, Dale R. Worley
wrote:
Interesting. The documentation for 4.2.53(1) says this about
parameter
assignments generally, with no special rules for compound assignments:
All
values undergo tilde expansion, para
> On Jul 27, 2020, at 1:31 AM, Dale R. Worley wrote:
>
> Alexey Izbyshev writes:
>> I have a question about the following behavior:
>>
>> $ Z='a b'
>> $ A=(X=$Z)
>> $ declare -p A
>> declare -a A=([0]="X=a b")
>> $ A=(X$Z)
>> $ declare -p A
>> declare -a A=([0]="Xa" [1]="b")
>>
>> I find it su
11 matches
Mail list logo
