Ville M. Vainio's suggests that c.find_b() and c.find_h() be used. See post:
http://groups.google.com/group/leo-editor/tree/browse_frm/thread/9894b776c2afffb2/f463563852449389?rnum=1&_done=%2Fgroup%2Fleo-editor%2Fbrowse_frm%2Fthread%2F9894b776c2afffb2%3F#doc_57e3cd4de8201b9b Looking at either c.find_b() or c.find_h() you can see the recommendation: You can chain find_h / find_b with select_h / select_b like this to refine an outline search:: pl = c.find_h('@thin.*py').select_h('class.*').select_b('import (.*)') So I tried a few simple tests using select_b() and select_h(). I found that select_b() works just as I would expect, but select_h() surprised me. Puzzled I looked at the definition of select_h() and found "Find immediate child nodes of nodes in poslist with regex." Wouldn't it be better for select_h() to be consistent with select_b()? Wouldn't it be better for them both to search the nodes in poslist? Using the Nav tab on LeoPyRef.leo and leoPluginsRef.leo for 4.8-final, I could not find a single use of select_h(). Hopefully, there is time to change select_h() before there are too many dependencies on its current behavior. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
