@Thomas : For leointeg, it just relays the commands to the leoBridge instance the server is running. So leointeg already ran any scripts from it's first inception back in 2021. Just like it would normally in Leo, via @buttons, @commands, or just hittin CTRL+B with focus on onw of LeoInteg's panel. :)
For LeoJS, it will run javascript scripts instead of python scripts. @Edward : Thanks! Yes I noticed your request for review, hehe , i'll get on it and test those new features this evening. It's been quite a cleanup/rehaul for leoFind.py those past few weeks! Can't wait to wrap this up and transliterate all those updates into leojs!! :) Thanks again! I really appreciate your comments and attention to all those details! Félix On Friday, February 3, 2023 at 5:20:36 PM UTC-5 Edward K. Ream wrote: > On Fri, Feb 3, 2023 at 4:11 PM Edward K. Ream <edre...@gmail.com> wrote: > > > The original reason for the PR was that ctrl-clicking, say, _MyClass > wouldn't work. The old code only searched for def _myClass, not class > _MyClass. The new (simpler!) code tries more search patterns. > > Oops. I should have said, def _*M*yClass. > > Also, I forgot to mention that the new code searches for assignments > (aliases) as well. So ctrl-clicking _MyClass will find this assignment: > > class AnotherClass: > @others > > _MyClass = AnotherClass > > As before, the new code will conduct *alt searches* for defs. For > example, if you search for open_with_file_name Leo will find the node > containing def openWithFileName. > > Happily, the machinery to conduct alt searches is much simpler in the new > code. > > 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/e769c31e-b247-45a8-9aa9-effc04f70809n%40googlegroups.com.
