Dear Juergen,
The default behavior now works as I would expect. Thanks a lot!
Blake
On Sun, Sep 14, 2014 at 9:36 AM, Juergen Sauermann <
juergen.sauerm...@t-online.de> wrote:
> Hi Blake,
>
> done in SVN 472. See the new preferences file.
> You can now choose between the old behavior, always
Hi Blake,
done in SVN 472. See the new preferences file.
You can now choose between the old behavior, always inserting the
function text and inserting the function text only if the function
has changed.
/// Jürgen
On 09/1
Dear Juergen,
Having a configuration option to have history only keep what I type, and
not anything output by the system, is perfect.
Thanks.
Blake
On Sat, Sep 13, 2014 at 8:03 AM, Juergen Sauermann <
juergen.sauerm...@t-online.de> wrote:
> Hi Blake,
>
> I believe it is more a matter of pers
Hi Blake,
I believe it is more a matter of personal preferences how the
history is used.
I am more of a cut-and-paste guy than a scroll-up-and-down
person and I find
it convenient to show the history first and cut-and-paste it then.
I bel
Dear Juergen,
I think there is a significant difference in philosophy here. I think a
history mechanism should keep a history of what _I_ type, but _not_ what is
output by the system. If I were to type in a new function, it should be
added to history. But if I list an existing function, it is d
Hi Blake,
this is actually on purpose. The reason is replay of (or
cut-and-paste from) history files.
Previously (libreadline) only the opening of the function (∇test)
would be stored in the history.
The subsequent lines would be eaten by the ∇
