Ha! I searched LeoPyRef.leo and didn't think about leoSettings.leo. One of those weird things! And yes, I found nothing about it in LeoDocs.
I wonder how we could make it clear to newcomers that this kind of search can be useful. On Thursday, October 15, 2020 at 10:05:36 AM UTC-4, Edward K. Ream wrote: > > On Thu, Oct 15, 2020 at 8:22 AM Thomas Passin <[email protected] > <javascript:>> wrote: > >> Thanks, Edward. BTW, I can't find any reference to it in the docs I >> looked at. I had to search LeoPyRef.leo to find it and the values it >> recognizes. Of course, I would have had no idea even to look for it if you >> hadn't clued me in. >> > > This is a perennial problem. > > I have this theory that the best way to organize and find data is by using > outlines. Yeah, it's kinda silly of me. I also have this theory that words > words words are hard to digest and understand. > > Imo, those theories imply that the best way to understand Leo's options is > to search leoSettings.leo. Using "headline-only" searches helps. When you > search for "undo", you will find: > > leoSettings.leo#@settings-->Command options-->Undo settings > > That node has only three children, so it shouldn't be *that* hard to > discover that @string undo-granularity might have something to do with your > issue. > > Yes, all this is likely clear in retrospect, but still, searching > leoSettings.leo is typically a good idea. And a better idea than searching > LeoDocs.leo. > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/c521269a-ffca-41ce-a023-6ad5975baf4do%40googlegroups.com.
