On Tuesday, June 27, 2017 at 9:05:57 AM UTC-5, Edward K. Ream wrote: > > This branch will be devoted to the following items: > > # 510: <https://github.com/leo-editor/leo-editor/issues/510>bindings to > commands created in plugins (sometimes?) don't work > <https://github.com/leo-editor/leo-editor/issues/510> >
This part of the project has been completed. No real changes were made, except to the quicksearch plugin. After considerable study, the conclusions is that plugins should not create bindings by calling k.registerCommand. Such bindings happen "too late" in the startup process to be over-ridden in settings files. Instead, plugins can define *suggested* bindings in leoSettings.leo. *Note*: The mod_scripting plugins creates bindings from @button and @command nodes. Again, these are "late" bindings that can not be over-ridden in settings files. I don't believe this is a big problem. The problem arises because Leo loads plugins after loading all outlines. It's not a direct consequence of using settings files. I am going to postpone the following items until possibly much later: > #467: File-open-by-name command: Add a setting to define preferred > directory <https://github.com/leo-editor/leo-editor/issues/467> > > #417: Complete reload-settings > <https://github.com/leo-editor/leo-editor/issues/417> > Leo now has two new command-line options. These provide more detail than the print-binding or print-settings commands, but only for a *single *setting or binding. Examples: --trace-setting=http-port # setting name --trace-setting=cff # command name --trace-binding=shift-ctrl-f # key binding 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.
