Lister: cannot search double backslash

[blindvic]

When viewing a text file using Lister, it doesn't search correctly double backslash.
Pressing Ctrl+F and entering '\\' makes lister to find single backslash '\'. If enter '\\\' or '\\\\' it looks for these strings as expected.

[Hacker]

blindvic,

'\\\\' it looks for these strings

Not confirmed. "\\\\" looks for two backslashes (not four), as described in the help file.

Roman

[Jungle]

If a text file contains e.g. text d:\test, the search will be successful for both search patterns d:\ and d:\\, but unsuccessfull e.g. for the pattern d:\t.
I think if help file definitely says that pattern \\ corresponts to single backslash, so search should not be successful for d:\ pattern.

[Bartusg]

Request: Could text be defined as everything one can type and find in a basic text-editor? Everything else eg line-breaks would then be searchable using regex.
I do happen to have a c:\test dir for trying out portable apps; searching this string in regedit is straightforward, in TC I had to do some thorough reading to discover I was in fact searching for Line Breaks.
Of course this would involve both the search dialog and the Lister view and find function (F3).

[Hacker]

Jungle,

search should not be successful for d:\ pattern

Why not? d: is in the text file.

Bartusg,

I do happen to have a c:\test dir for trying out portable apps; searching this string in regedit is straightforward, in TC I had to do some thorough reading to discover I was in fact searching for line breaks.

Tabs, actually.

Roman

[Bartusg]

Tabs, actually.

That is the problem exactly, by searching strings like 'c:\test', 'd:\nieuwe profeten' or 'h:\disoneisharmless' one has to become a very particular kind of reader to scan for tab or line break collisions (yes/yes/no).
In other words I don't want to have do such scanning, that's what I have a computer for.

[sqa_wizard]

2Bartusg
This is the way it is designed and well documented.
It just works the way like powerful text editors do.

In other words I don't want to have do such scanning

The only thing you have to look for is:
If you are searching for a backslash, you have to double it ...

[Bartusg]

This is the way it is designed and well documented.

The point I try to make is that the design could be a bit more logical. Documentation would have to change, but for that we have text editors.

It just works the way like powerful text editors do.

Please read: everything one can type and find in a basic text-editor... I was thinking of Notepad, but take a look at: http://files.myopera.com/bartgzn/files/Notepad++.JPG

The only thing you have to look for is:
If you are searching for a backslash, you have to double it ...

A backslash is something I can type and find in a simple text editor, and probably in Notepad++ too.
From another perspective, would you consider renting a car that can only be driven safely when properly reading the manual?

[petermad]

Well this isn't a bug, but I can support if Bartusg puts it in the Suggestions section as an optional feature - either by a wincmd.ini setting, or better by an option in the search dialogs (also Find files dialog) - an option that sticks between sessions.

[Bartusg]

but I can support if Bartusg puts it in the Suggestions section

Thanks petermad, let's give that a try!