I see how a vi_leoSettings.leo separates out the released vi key
bindings but how would someone disable the active EKR bindings and
activate the vi bindings from their myLeoSettings.leo (or
myVi_leoSettings.leo) so that installing new versions of the trunk
won't revert back to the EKR bindings?
Copying a set of key bindings from leoSettings.leo to
myLeoSettings.leo to enable them means that users must be made aware
when updates to those key bindings are made to the trunk and so they
can copy them again to their myLeoSettings.leo file. Not an ideal
situation.
Is there any chance that a
...or maybe a way to include other setting files (akin to plugins),
then you could include a vileoSettings.leo file
(*grin* mimicking my leo Settings naming)
On Jun 18, 12:38 pm, TL [EMAIL PROTECTED] wrote:
Copying a set of key bindings from leoSettings.leo to
myLeoSettings.leo to enable them
