> It would be more accurate to say that settings can only be read > reliably during *startup*. During startup, many settings get cached > for efficiency/convenience reasons, so changing the settings later > will have no effect.
I see, I had only read leoConfig.py and thought those settings Dicts and Lists must be mutable (they are, so why not invalidate the cache from the set-functions?). Anyway, I will continue reading the source to understand better. > Let me know if there is a setting that should be settable after > startup, and I'll see what I can do. I was writing a command 'toggle-log-pane' to 'fully-expand-log-pane' and 'hide-log-pane' so when that seemed to work I made a shortcut for this new command. Stubornly I refused to having to restart Leo to get this key-binding to work, and started digging for information. To experiment with the effects of editing with new shortcuts, @button set-shortcuts would be useful, but involves parsing the @shortcuts syntax, so I thought why not reuse the existing code?! Then after the traces from the config-classes told me the new settings where set but they didn't work I came here for help. The code could fallback to the cached settings if a local dict has no such setting. I'll try to write a button that resets already known bindings, this should be possible right? Lo -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
