Total Commander

Try doing shift+scroll in a view with search results. Poof, they are gone.

If you do shift+scroll in a view with search results to go back, you can never go "forward" to your search results. This is especially "fun" when I've got a list of results that took a long time searching, and I accidentally hold shift while trying to scroll through the list. I basically had to re-execute the search, which was a waste time and power.

Can it be fixed so that shift+scroll going forward, can also go forward to the search results after going back from it?

What should shift-scroll do ?
I know no such function in TC
and I never hit shift while scrolling in search results.

2Thany
Shift+scrool does nothing in the search result itself, but maybe you mean in the search result fed to listbox?

In search result fed to listbox Shift+scroll cycles through the history, and since search result fed to listbox is NOT part of the history, you can not get back to that search result - in fact if you leave the search result fed to listbox in any way, you can never go back.


2Horst.Epp

History.txt wrote: New in Total Commander 6.0 final (17.11.03):
.
[User interface]
- Shift+Mouse wheel activates history (go back/forward)

Or in the full history ( https://madsenworld.dk/tcmd/TCHistory.txt :

01.10.03 Release Total Commander 6.0 beta 3
01.10.03 Added: Shift+Mouse wheel activates history (go back/forward)

First of all - use "Search in separate Process..." so after "Feed to listbox" search results window stay open.

It's not a bug - Shift+Scroll goes through directory history. As petermad wrote, search results are not part of the directory history, because the history only saves the location, not the content of the list.

@ghisler, you're describing it in a way that it *is* a bug

Anyway, it's an annoying problem to have to deal with, and if you can go back, you should also be able to go forward. As a user, I don't care that it doesn't store the content. It sounds to me like it probably should, if that's what it takes.

Alternatively, if moving away from the search results, display a confirmation box. It's a bit crappier for when you genuinely want to get away from the search results, but it means a search that took half an hour to complete, might not need to be performed again.

Thany wrote: ↑2020-09-25, 08:21 UTC Alternatively, if moving away from the search results, display a confirmation box. It's a bit crappier for when you genuinely want to get away from the search results, but it means a search that took half an hour to complete, might not need to be performed again.

And why don't you use "Search in separate Process..." as Gral suggested above ?
Then you never loose search results.

2Horst.Epp
Of course you can lose the results in separate search, just press Escape one time too many. The window isn't fixed in place, it's loose ;-P and there is no way to lock or pin it.

Usher wrote: ↑2020-09-25, 22:14 UTC 2Horst.Epp
Of course you can lose the results in separate search, just press Escape one time too many. The window isn't fixed in place, it's loose ;-P and there is no way to lock or pin it.

I don't know how you are working but I never had closed the separate Search results by accident
and I use that mode all the time.
No program logic can prevent fools to make their mistakes

2Horst.Epp
Well, it's obvious for intensive search with highly inaccurate search criteria. I switch between multiple TC Search and TC Lister windows and sometimes I close one window too many by mistake.
I wish I could pin some results. "Feed to listbox" is only a poor workaround - you can't go back when searching in found results.

Horst.Epp wrote: ↑2020-09-25, 09:37 UTC

Thany wrote: ↑2020-09-25, 08:21 UTC Alternatively, if moving away from the search results, display a confirmation box. It's a bit crappier for when you genuinely want to get away from the search results, but it means a search that took half an hour to complete, might not need to be performed again.

And why don't you use "Search in separate Process..." as Gral suggested above ?
Then you never loose search results.

Why don't I? Because I don't know of its existence. Where is that? What does it do? Can I still "feed to listbox" any search results? And if it's better, why isn't this the standard?

More importantly, why does it persist search results? Or even more important, why are search results in same process (I guess) volatile?

Why don't I? Because I don't know of its existence. Where is that?

Standard menu: "Commands" -> "Search in separate Process \ Alt+Shift+F7"

What does it do?

Performs the Search in a window that is not modal to TC, so that you can keep working in TC, and you can open multiple search instances.

Can I still "feed to listbox" any search results?

Yes.

And if it's better, why isn't this the standard?

Because iot was introduced years later that the modal search, and Ghisler don't like to break backward compatability

"Search in separate process" was introduced in TC 8.50 public beta 1

History.txt wrote:05.07.13 Added: Menu item "Search in separate process" in menu "Commands", new hotkey Alt+Shift+F7 (32/64)

You can make it your standard by assigning the command cm_SearchStandalone to Alt+F7

why are search results in same process (I guess) volatile

They are not, but in order to use TC you have to close the search window to keep working in TC

Last search result has been shown since TC 7.56 beta 1

history.txt wrote:10.11.10 Added: Find files: Remember last search results when using "Go to file" or "Cancel" (but not when using "Feed to listbox"). Turn off with SearchKeepLast=0 in wincmd.ini