>
> There is certainly unexpected behavior going on here. I'll take a closer
> look, but fixes will have to wait until bash-4.2 (or a patch to bash-4.1
> if the problem is widespread).
4.2 would be fine but not before please! I'm still scheming how best put
this feature to "good" use in my "frie
On 12/23/09 10:06 AM, Jonathan wrote:
> On Dec 23, 7:34 am, Chet Ramey wrote:
>> I would think so, since you've inserted a command continuation (the escaped
>> newline) into the command via the alias. It's the same as if you had typed
>>
>> *$* echo \
>> *>* Hello, World!
>>
>> The only unexpecte
On Dec 23, 7:34 am, Chet Ramey wrote:
> I would think so, since you've inserted a command continuation (the escaped
> newline) into the command via the alias. It's the same as if you had typed
>
> *$* echo \
> *>* Hello, World!
>
> The only unexpected part is the re-issuing of $PS1 as opposed to
On 12/22/09 5:18 PM, Jonathan Claggett wrote:
> Hi all,
>
> I'm not sure if this is a bug or not but it certainly caught me by surprise.
> I accidentally created an alias ending with a backslash and a newline today
> and the resulting alias proceeded to grab the text on the line _after_ I ran
> it
Hi all,
I'm not sure if this is a bug or not but it certainly caught me by surprise.
I accidentally created an alias ending with a backslash and a newline today
and the resulting alias proceeded to grab the text on the line _after_ I ran
it. For example:
*$* echo $BASH_VERSION
4.0.33(1)-release
*
