On 12/16/14 2:53 AM, Dan Douglas wrote:
> On Sunday, December 14, 2014 02:39:29 PM Chet Ramey wrote:
>> And we get to the fundamental issue. Is it appropriate to require
>> arguments to declaration commands to be valid assignment statements when
>> the parser sees them, instead of when the builtin
On 12/16/14 7:30 AM, Stephane Chazelas wrote:
>> * This solves the problem without breaking backwards compatibility and
>> allows
>>declare -p output to continue to function.
> [...]
>
> Well, if "declare -p" continues to function which is not what I
> understand your proposal to do, then:
On 12/17/14 3:58 AM, konsolebox wrote:
> On Mon, Dec 15, 2014 at 4:34 AM, Chet Ramey wrote:
>> It does implement `emulated behavior of normal assignments'. The question
>> is whether or not it should do that after having had its arguments undergo
>> one round of word expansion.
>
> After studyin
On 12/21/14 3:28 PM, Richard W. Marsden wrote:
> steps to produce
>
> hide cursor
> setterm -cursor off
>
> call the bash built-in read command as follows: silent, wait 1 second, read
> 1 character to variable KEY
> read -s -t 1 -n 1 KEY
>
> while the read command is in a loop, control +
Hey,
without checking the source: reset utility from ncurses fixes your term.
this one is reproducible.
cheers,
pg
On Sun, Dec 21, 2014 at 9:28 PM, Richard W. Marsden wrote:
> steps to produce
>
> hide cursor
> setterm -cursor off
>
> call the bash built-in read command as follows: sil
