data returned by search

[HansBKK]

I'm just starting to realize the possibilities offered by the search function, especially since I've been using a standardized naming syntax in my node headers.

There may be a very good reason why the the search results return separate results for each clone, but I'm finding that doesn't help my use case, and has become redundant since finding goto-next-clone, which I have bound to Alt-N.

Is there a way to turn this off via a user setting I haven't found yet?

If not, consider this a proposed wishlist, and if in fact there isn't a good reason for it working that way within the one-node paradigm, perhaps turning it off by default?

[HansBKK]

I imagine this is relevant?

> The c.all_unique_positions() iterator uses node identity to remove duplicate nodes, but that's about the only way identity will
come into the picture.

> That is, searching by special-purpose Leo scripts. We aren't talking about Leo's search command here

[HansBKK]

https://bugs.launchpad.net/leo-editor/+bug/909278

[Edward K. Ream]

On Sat, Dec 17, 2011 at 5:41 PM, HansBKK <han...@gmail.com> wrote:
> I'm just starting to realize the possibilities offered by the search
> function, especially since I've been using a standardized naming syntax in
> my node headers.
>
> There may be a very good reason why the the search results return separate
> results for each clone, but I'm finding that doesn't help my use case, and
> has become redundant since finding goto-next-clone, which I have bound to
> Alt-N.

The clone-find-all command returns one result for each node, no matter
how many times it is cloned. This is usually good enough.

As you imply, it would be conceivable to add a "once-per-clone"
checkbox in the Find dialog, but this isn't going to happen any time
soon.

Edward

[Terry Brown]

On Fri, 30 Dec 2011 10:35:44 -0500
"Edward K. Ream" <edre...@gmail.com> wrote:

> On Sat, Dec 17, 2011 at 5:41 PM, HansBKK <han...@gmail.com> wrote:
> > I'm just starting to realize the possibilities offered by the search
> > function, especially since I've been using a standardized naming syntax in
> > my node headers.
>

> The clone-find-all command returns one result for each node, no matter
> how many times it is cloned. This is usually good enough.

I suspect the OP was talking about the results in the Nav pane? The
Nav pane is much better navigation wise than clone-find-all, and having
it return unique hits only would be useful.

What's the best way to add settings to the Nav pane? Currently the
only 'setting' I can recall is that search strings starting with "r:"
are treated as regular expressions. We could add more flags that way
("u:" for unique, "ru:" for unique and regex, etc.), or add a settings
panel to the Nav. pane, which would eat some screen space, but could be
collapseable.

Cheers -Terry

[viva...@gmail.com]

I recommend adding string flags and a 'quick help' feature, perhaps behind rclick...

--
You received this message because you are subscribed to the Google Groups "leo-editor" group.
To post to this group, send email to leo-e...@googlegroups.com.
To unsubscribe from this group, send email to leo-editor+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.

[HansBKK]

Yes, sorry I didn't explicitly state this was wrt the Nav pane.

This also made me realize that limiting the nav to a single clone result brings up the question

which location to bring the outline to when clicking in the nav?

I would have thought

first instance after current cursor location

would make sense, but perhaps that's difficult, or others may disagree as to what's "logical".

In any case I agree NBD if it isn't implemented; thanks for the reminder of the > clone-find-all command, which is in fact often more useful than just navigating via find-quick-selected.