docs: selection

[chapmanjacobd]

What actions do not clear the selection afterwards?

Also, it would be useful to log the count of selected whenever the count of result is logged so that it might be more obvious when the selection is not cleared.

Count of selection seems like a more important thing to log than many of the other things that are logged by default. Sometimes logging too much can make it harder to see important stuff--though the colors definitely help

[scrubbbbs]

-select-* appends to the current selection, except of course -select-none.

Anything that produces a result/group set should clear the selection, otherwise that's a bug. The reasoning is that when you have both a selection and result, some commands get ambiguous (e.g. when -show is used what do you see, the selection or result...).

The one exception I found was -nuke which clears it. In that case it makes sense since it invalidates the selection.

I think that logic is isn't too convoluted, but yes it should be documented. I've started the wiki so we can start listing out some of these things that are probably too detailed for a -help page.

Yes the logging is a big chaotic, I have mostly focused on logging something for anything that could take a long time, it bothers me a lot when there is a long pause with no logging.

I do have a small bug in my brain to removing extra logging or move it to the debug log when I come across it. Eventually the debug logging will be hidden.