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 ∇
With the new history control, none of the control-character shortcuts don't
work anymore, including C-p, C-n, C-f, C-b, C-a, C-e, C-k and C-y.
Could this be added? I suppose it's a simple matter of adding mappings to
existing functions.
Regards,
Elias
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,
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,
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
The subject says it all.
I have a glyph setup for my MacAplAlt but it must be the wrong key code.
Because if I use it I get Offending token…..SYNTAX ERROR.
So what is the correct one to use please?
Thanks….
Peter
U+25CA (from src/Avec.def)
Great thanks that fixed it.
On 2014-09-13, at 6:58 PM, David B. Lamkins wrote:
> U+25CA (from src/Avec.def)
