Live Filtering and the dot

[MBaas]

I noticed a little problem as I attempted to filter for a certain file WITH extension:

• I entered the name into the LFB: DUI and the list only showed matching files)
• Next was the dot: DUI. - and the list was emptied
• Next the first character of the extension: DUI.d - and the list showed two matching files.

So why was it emptied in step 2? (Actually this had me so confused that I first did not even think about trying to continue my typing)

Hopefully it's a bug and not a feature!

[Horst]

This is not an error and expected behaviour.
There can be files with a dot at the end and no extensions.
Windows / Linux users often have config files named like this.

[RalphM]

I think it is a feature as the "." without anything following represents anything without an extension.

[admin]

So it is.

[MBaas]

I understand - but this seems a bit contradictory, as "foo" is not interpreted as "names ending with `foo`", nor is "foo.a" - so it seems a bit odd that "foo." would suddenly be. But I see the point (ha, pun intended) about there being no extension - but then I guess a similar case could be constructed when the filter for "foo.doc" also shows ".docx" files and we accept it - so why can't file with an extension be included as well?. Maybe an explicit symbol for "end of match" (perhaps ":") would be more consistent...

Another example: how can I search a folder for ALL files w/o extension? Surprisingly "." alone doesn't do it - as that includes only filenames WITH an extension and EXCLUDES those without one...

[admin]

*.

[MBaas]

Oh well, you've beaten me, I give up. (grumble, grumble)