An '<' character on 'Search for' causes an 'error' ?

English support forum

Moderators: Hacker, petermad, Stefan2, white

Post Reply
Farri
Junior Member
Junior Member
Posts: 7
Joined: 2010-06-17, 21:34 UTC

An '<' character on 'Search for' causes an 'error' ?

Post by *Farri »

I'm not sure if this is by design or a bug. Also I'm not found a post with this problem; sorry if is a duplicate question.

I'm using Total Commander 8.51a, but the on (some) previous versions the bug is the same.

If I put a '<' (without the quotes) as the first character on the field 'Search for', Total Commander 'ticks' the option for RegEx and ignore this character.

I've found this problem by hazard (I was trying search for text, instead search for a file); I know the the symbol '<' or '>' can't be used on filenames because those symbols are used for redirecting stanard input and output.
User avatar
Stefan2
Power Member
Power Member
Posts: 4281
Joined: 2007-09-13, 22:20 UTC
Location: Europa

Re: An invalid character on 'Search for' causes an "err

Post by *Stefan2 »

Farri wrote: If I put a '<' (without the quotes) as the first character on the field 'Search for', Total Commander 'ticks' the option for RegEx and ignore this character.
And what is the actual error now? That RegEx is checked now?

It's by design that '<' enables RegEx, see the Help, e.g.


Find files: General
Search in:
c:\testdir\<regular expression ----> Searches "c:\testdir" using regular expression



Selecting files
You can now also use regular expressions. They need to be started with a "<" character, to distinguish them from normal search strings.




For an start to search for more about this
go to the Regular expressions help section:
Total Commander supports regular expressions in the following functions:
- Commands - Search (in file name and file contents)
- In Lister
- In the Multi-Rename tool
- In the selection dialog

.
Farri
Junior Member
Junior Member
Posts: 7
Joined: 2010-06-17, 21:34 UTC

Post by *Farri »

Sorry, then is not a error but is the action intended.

The title of post should ended in a question mark, but I made a mistake.

Thanks a lot for your answer.
Post Reply