On Tue, Jun 20, 2017 at 3:38 AM, jkn <[email protected]> wrote: I haven't been particularly following the discussion about toggle-split > direction, but I think I see things a little different to you. > Maybe ;-)
The Bash history facility (for example) use a file (~/.bash-history by > default) which stores the last N commands entered. So I had in mind > something similar, which could be loaded at the start of a session, > maintained as commands are entered and executed, and saved before exit. I > would keep the number of commands stored relatively small (N = 50 or 100, > perhaps). > > The 'problem' then would be: how, at the start of a session say, would the > commands in @data command-history be 'reconciled' with the contents of the > .history file? One could imagine them being concatenated, but other schemes > are possible, and I am not sure there is a definitively best answer. > Imo, settings are incompatible with automatic operation. Settings promise stability. Updating them automagically breaks that promise. Imo, the history settings are good enough. I have no plans to replace them. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
