I've been using them more and more as a kind of pseudo-code to improve readability. @Edward has said he's been going in the other direction, using @other more. I mean, something like this speaks more to the program flow than spelling out all the details inline:
<< init >> << load data >> << restructure data >> << create formatted output >> << write output >> Yes, you could make all those sections into functions or methods of the same name, but that can add complication and take longer. Or it could be be done in a later refactoring if that seems worthwhile. or if the sub-block might be useful somewhere else, too. On Saturday, March 5, 2022 at 9:08:49 AM UTC-5 jkn wrote: > On Friday, March 4, 2022 at 4:27:36 PM UTC [email protected] wrote: > >> : ) Let us know if there are cases it doesn't work for you, so the code >> can be adjusted. So far it has worked for me every time. The named >> section does have to be in the clicked node's subtree, but that's a normal >> requirement for a named section anyway. >> >> On Friday, March 4, 2022 at 10:26:48 AM UTC-5 jkn wrote: >> >>> On Friday, March 4, 2022 at 3:01:31 PM UTC [email protected] wrote: >>> >>>> New in the devel branch - when you CTRL-click on the body on the line >>>> containing a <<named section>>, the selected node will change to the >>>> named >>>> section's node. >>>> >>>> The old behavior of CTRL-click navigating to a UNL or URL is unchanged. >>>> >>> >>> That sounds really useful, thanks! >>> >>> J^n >>> >>> >> > TBH I don't use sections much at the moment, but it's the sort of > enhancement I like to see. I use CTRL-click on URLs a lot. > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/b061b4d9-4954-4c1d-9e62-23e340324377n%40googlegroups.com.
