On Mon, Jun 26, 2017 at 8:30 AM, Terry Brown <[email protected]> wrote:
>
> Would it be fair to say that *if* a plug-in wished to define a default
> binding for a command, it should do it in leoSettings.leo, which users
> could override in myLeoSettings.leo?
>
Yes.
>
> I guess I'm not sure what you mean by "prevent"
I believe it's a symptom of #510.
> And also, that in this particular case, you could have moved the
> binding there to avoid the sudden change in established defaults
Good idea. I'm not sure that's going to fix #510, but it should be done
anyway.
> Finally, I'm sure you can define bindings for plugin commands in
> myLeoSettings.leo, e.g. I have:
>
> find-quick-timeline = Ctrl-Shift-T
>
That's why I said (sometimes) in the title for #510.
Something strange may be going on.
so wonder if that part is either people struggling to remember how to
> define bindings (as above in @settings-->@keys-->@shortcuts
No. It's something else. This doesn't work for me:
find-quick-selected = Ctrl-Shift-F
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.
