On Wed, Jul 5, 2023 at 8:48 AM Thomas Passin <[email protected]> wrote:
> I disagree about removing the *@string unl-status-kind* setting. I get > the most value from the status bar when I can see the path of a node. A > gnx-based unl tells me nothing useful. If I want to see if the node is in > the outline I think it is, I can look at its tab or the title bar of the > Leo window. The gnx part is useless for orienting me within an outline. I > **really want** to see the path-based expression in there. Alright. Let's leave this setting in. What about the other setting, @bool full-unl-paths = True? It's never made much sense to me. It does not affect gnx-based unls. As for your expression paths = list(reversed([z.h for z in > p.self_and_parents()])), > > there is no need to cast it to a list. > This is the second time you have made this mistaken assertion. reversed is a generator: print(reversed(['a', 'b'])) <list_reverseiterator object at 0x00000218572299C0> ...let's have a Leo method to return it. No reason for everybody to roll > their own. > I don't want to encourage path-based unls :-) I mentioned this statement only to show how *you* could maintain compatibility in your plugins. 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/CAMF8tS0u86k2O3LB9j1oxBnCZAB1-7f0h9Qqf7OxZunLznN3QA%40mail.gmail.com.
