PS: Just realised/remembered - one reason for preferring the @shortcuts node method is that only it AFAIK allows the use of 'body', 'tree' etc. modifiers...
command_name ! body = KeyStroke command_name ! tree = AnotherKeyStroke On Thursday, June 26, 2025 at 12:10:57 PM UTC+1 jkn wrote: > On Thursday, June 26, 2025 at 11:50:13 AM UTC+1 Edward K. Ream wrote: > > On Thu, Jun 26, 2025 at 5:35 AM jkn wrote: > > Thank you. Apologies if it has taken me a while to provide the necessary > information. > > > NP. It's all good. > > The problem arises because your myLeoSettings.leo uses an @shortcuts node > to bind keys to your `@command` scripts. Fixing this buglet may not be > straightforward. We shall see. > > The workaround (and imo best practice) would to create the bindings in the > `@command` scripts: > > @command test_cmd1 @key=Ctrl+Alt+1 > @command test_cmd2 @key=Ctrl+Alt+2 > > > Yes, I have very nearly done this a couple of times ... as I say above, I > am not 100% sure why I have some one way, and some the other. This report > was originally to try and understand what was going on, and why. FWIW I > would have thought that the separated use of @shortcuts was more 'best > practice', but there you go... > > BTW, I can confirm the behaviour of (merged) > https://github.com/leo-editor/leo-editor/pull/4378 seems to correct issue > https://github.com/leo-editor/leo-editor/pull/4378. Sorry I didn't get > chance to review the PR, and thanks to Thomas for doing so. > > Thanks > J^n > > > -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/b0118374-d0ab-434c-824c-eb79a68ba828n%40googlegroups.com.
