Find As You Type - Bug

therube · Post by **therube** » 15 Feb 2007, 17:48

Find As You Type - Bug

FAYT, that is probably not the correct terminology, but ...

When traversing a directory, if there exists a file name with no extension, & the same named file with an extension, the DOT key does not advance to the next file in sequence till you type the particular character that follows DOT.

This is more observable if file names are sorted alphabetically.

If you were looking for a particular file, & the files were not listed alphabetically, you could easily mistakenly think that no further files in sequence existed.

Forinstance, typing ...

Code: Select all

A P 2 S A           leaves you at AP2SA
A P 2 S A .         (with the dot) still leaves you at AP2SA
A P 2 S A . 1       will advance to AP2SA.103102

Typing AP2SA. should match AP2SA.103102 & should advance you to that spot.
SS25rc2 does not do this. SS2.0 does.

Code: Select all

AJULIAN
albert
albert.saf
albert.sort
AP2SA
AP2SA.103102
AP2SA.1211
AP2SL
AP2XA
AP2XA.103102
AP2XA.1211
ap2xa.printout
AP6
ap6.o
ap6.o.2big.zip
ap6.o.2big2.Z
AP6A
AP6A.112803
ap6a.o
ap6a.o.2big.z
ap6a.o.3.Z
AP6L
AP6L.humha
ap6l.MAN
ap6l.o
ascii
atafaq.Z

therube · Post by **therube** » 15 Feb 2007, 21:51

Further, this only occurs if the current cursor location (focus) causes the first found file, to be one with no extension.

If FAYT brings you first to a file with an extension, this will not occur.

So if my list were sorted in descending order, focus on the first file in the list, typing AP2SA. would successfully take you to AP2SA.103102.

Post by **Jan Rysavy** » 16 Feb 2007, 09:33

Hello, it is not a bug, it is feature introduced in Salamander 2.5 RC1

http://www.altap.cz/salam_en/help/salam ... search.htm
"Trailing dot (.) character is ignored when name has no extension."

Usage:

Three names (sorted by Name):
aa
aab
aac

aac is focused

you can enter aa. to focus the aa file.

Hint: you can press the Home/End key during the Quick Search mode.

SvA · Post by **SvA** » 16 Feb 2007, 15:37

I think you should reconsider the choice for that character and use some character which is not a valid filename character for that purpose. I suggest '|'.

BTW: Is there any reason you invented three generic characters ('/', '\', '<') to mean the same as '*' in a file mask? Why did you not use file masks, as everybody is familar to them already?

therube · Post by **therube** » 16 Feb 2007, 17:34

Thanks.
I see you're reasoning, though I'll have to dwell on it before it sets in.
Just doesn't seem "natural"?

Post by **Jan Rysavy** » 19 Feb 2007, 08:02

SvA wrote:BTW: Is there any reason you invented three generic characters ('/', '\', '<') to mean the same as '*' in a file mask? Why did you not use file masks, as everybody is familar to them already?

Yes, there is a reason: national keyboard layouts. For example the '<' is there for German users of Salamander because the '/' and '\' are not accessible by one stroke.

SvA · Post by **SvA** » 19 Feb 2007, 17:49

Jan Rysavy wrote:Yes, there is a reason: national keyboard layouts. For example the '<' is there for German users of Salamander because the '/' and '\' are not accessible by one stroke.

Yes, I remember this from the corresponding thread. But why did you not use '*' as wildcard character (at least in addition to the others) as everybody is used to this character anyway? (just curious / possible suggestion for improvement (ease of remembering how to use the feature))

Post by **Jan Rysavy** » 19 Feb 2007, 18:16

The '*' is not accessible in one stroke.

SvA · Post by **SvA** » 20 Feb 2007, 23:23

I am not talking about simplicity of accessing a key, but about consistency and simplicity of remembering how to access a feature.

Post by **Jan Rysavy** » 21 Feb 2007, 09:49

We can probably also enable '*' for this function, no problem.