Total Commander

You can't search for line breaks with regular expressions in Lister. Why? Lister only keeps a small part of the file around the current position in memory. Therefore I'm passing only single lines of text to regular expression searches. Even then the search mail fail if the match would be longer than 4kBytes.

xxxdo1 wrote: 2024-11-14, 01:20 UTC Adding too many checkbox options is not a good idea.
Regular expressions contain escape characters, and the two do not conflict.

Very interesting remark; it helped me to understand the following points.

First. You (and I) did not know what type of search we we using after many years with WC & TC. Most people assume it to be trivial literal search (case insensitive) - as in the great Norton Commander.

Second. Currently, we do not have literal search at all. Surprise!

Thiere must be a way to look for exactly given string.
So the title of this request might be: Add literal search method and make it the expected default.

Additionally, it might be mentioned in help that treatment of backslashes in escaped and regular expression searches is different.

xxxdo1 wrote: 2024-11-14, 01:20 UTC Adding too many checkbox options is not a good idea.
Regular expressions contain escape characters, and the two do not conflict.
In my usage, I use regular expressions when I need to escape characters, and for general searches I consider it disabled.

I agree with *xxxdo1 and others.
I've been a Totalcmd user for many years (aupa Norton Commander) and didn’t notice this behavior. My bad.
It would be great if it could be disabled in the .ini.

Thanks for listening.