>Someone else already provided a suitable answer. Continuing this
>conversation is not productive; it's quickly reaching dead horse
>territory.
>
>You might want to check out the latest devel branch snapshot, though.
It works! Thanks a lot.
Bug seems to be fixed in 2bfa477ae8878e21c0b15b5d66099c4c
On 12/3/14, 4:48 AM, Adam Ryczkowski wrote:
> I am trying to write a function that logs execution of the *next* line. The
> usage would be:
>
> #/bin/bash
> log=/tmp/mylog.log
> var1="some variable"
>
> log
> echo "Unfortunately this line gets executed twice" | tee -a
> /tmp/t
On 12/3/14, 9:52 AM, Askar Safin wrote:
>>> Please stop mischaracterizing the issue. It's not a bug: it's a case of
>>> konsole's mismatched expectations. Since the mechanism it uses is not
>>> documented, and relies on something in readline that is not documented, it
>>> can't fairly be called a
On Wed, Dec 03, 2014 at 06:51:08PM +0400, Gennady Kupava wrote:
> That was quite unexpected for me as a user. I checked sed script like this:
> echo "a
> b"| sed '/a/!d'
>
> And that implementation detail were highly unexpected... What is the point
> of multiline edits if quotes are unreliable for
>> Please stop mischaracterizing the issue. It's not a bug: it's a case of
>> konsole's mismatched expectations. Since the mechanism it uses is not
>> documented, and relies on something in readline that is not documented, it
>> can't fairly be called a bug.
>Should long text line move when user
>Bash has always performed history expansion a line at a time, as soon as
>the line is read from the current input source. One consequence of this,
>as you noted, is that it doesn't have access to the current quoting state.
>This is a limitation of the implementation.
That was quite unexpected fo
I am trying to write a function that logs execution of the *next* line.
The usage would be:
#/bin/bash
log=/tmp/mylog.log
var1="some variable"
log
echo "Unfortunately this line gets executed twice" | tee -a
/tmp/temp/bla-bla.tmp
The problem is that I can't reliably get to
On 12/3/14, 4:19 AM, Eduardo A. Bustamante López wrote:
> On Wed, Dec 03, 2014 at 08:57:26AM +0100, Piotr Grzybowski wrote:
>> Hey,
>>
>> I think in this case, history_expand lib/readline/histexpand.c:905 is
>> invoked with hstring="b\" | echo '!'", and goes wrongly into history
>> expansion.
>>
On Wed, Dec 3, 2014 at 10:19 AM, Eduardo A. Bustamante López
wrote:
> On Wed, Dec 03, 2014 at 08:57:26AM +0100, Piotr Grzybowski wrote:
>> I think in this case, history_expand lib/readline/histexpand.c:905 is
>> invoked with hstring="b\" | echo '!'", and goes wrongly into history
>> expansion. [.
On Wed, Dec 03, 2014 at 08:57:26AM +0100, Piotr Grzybowski wrote:
> Hey,
>
> I think in this case, history_expand lib/readline/histexpand.c:905 is
> invoked with hstring="b\" | echo '!'", and goes wrongly into history
> expansion.
> Not that I know how to fix it ;-)
Yes, the issue is tricky, bec
10 matches
Mail list logo
