D'accord.
On Sunday, May 26, 2024 at 1:51:56 PM UTC-4 Edward K. Ream wrote:
> On Sunday, May 26, 2024 at 12:42:11 PM UTC-5 Edward K. Ream wrote:
>
> > I don't like returning the results as cloned nodes...The Nav tab is
> better.
>
> I'm going to do the following:
>
> - Use the Nav tab If the
On Sunday, May 26, 2024 at 12:42:11 PM UTC-5 Edward K. Ream wrote:
> I don't like returning the results as cloned nodes...The Nav tab is
better.
I'm going to do the following:
- Use the Nav tab If the quicksearch plugin is active.
- Otherwise use clones.
That should make most people happy
On Sun, May 26, 2024 at 7:39 AM Thomas Passin wrote:
> I don't like returning the results as cloned nodes. That changes the
> outline, and a search should not do that. The search will change the focus
> to the new cloned results, which is distracting and unexpected. And later
> the user has to
I don't like returning the results as cloned nodes. That changes the
outline, and a search should not do that. The search will change the focus
to the new cloned results, which is distracting and unexpected. And later
the user has to remember to find and delete those clones without
On Sunday, May 26, 2024 at 6:02:37 AM UTC-5 Edward K. Ream wrote:
> *Aha 3*: Let the top-level results node (of either type) tell the user
about the new setting and the command to change it.
On second thought, delivering multiple results as cloned nodes (as in the
the clone-find command)
