[BUG] File folder(s) renamed to ending with a period (.) with Everything are not accessible.

[JTB3]

This violates default Windows behavior. Windows does not normally allow a user to create, rename, or open a folder with a period at the end of it. Still, Everything does allow for it - causing an accessibility error if opened. NTFS can support this, but the Windows shell and user interfaces do not support such names.

This error is easy to reproduce: Try to create or rename any Windows folder with a period at the end of it on the desktop or using File Explorer - you can't do it! Now try to rename a folder found in the results pane of Everything and add a period to the end of it, it allows for it! - but now the folder cannot be accessed with Windows Explorer!

Hopefully an easy fix, David...
-JT

[NotNull]

Why do you consider this to be a bug in Everything instead of being a bug in Windows Explorer?


The NTFS filesystem does support foldenames ending with a dot.
Windows itself supports multipe filesystem namespaces, among which Win32 namespace (syntax like \\?\C:\Windows) and posix (for unix/linux compatibility).
Both can create foldernames ending in a dot.


The following CMD commands create "dot folders"
(cygwin makes use of the posix namespace)

Code: Select all

md "\\?\T:\Folder ends with a dot."
c:\Tools\cygwin64\bin\mkdir.exe "Another dot folder."

[JTB3]

Why do you consider this to be a bug in Everything instead of being a bug in Windows Explorer?

Because without warning, Everything can create 'unusable' file folders that produce Windows shell errors (and also errors within Everything). At a minimum, IMHO, there should be a flag/setting that prevents this behavior (on by default) so users don't get faked out (advanced users could switch it off). It seems logical that Everything (by default) should perform consistently with and respect File Explorer/Shell naming conventions.

[therube]

I can see something here.
Given that there is difference in behavior between a directory name & a file name, one allowing the period & one not.

If not for that discrepancy...

[harryray2]

I quite like the fact that Everything can pick up on things like this.
Which made me wonder as to how one would search for this? I tried endwith:. but that didn't work.

[therube]

It should be finding it.

(And not that I'm sure what endwith: does particularly, cause it will also find something like: "/IRC.$/" - unless its' only dealing with, what are they calling it, "basename". :scratcheshead: I've just confused myself.)


Anyhow, to me, this is more "correct",

regex:^.*\.$

.

[harryray2]

Not really sure what that regex does, but it doesn't find any folder ending with .

[therube]

(Actually, the above [regex] would find a file or folder ending with a (.).)


Are you sure you actually created a directory name that ends with a (.)?

Code: Select all

test.
ddd.
dir_dot.

In this case, "test." is a file, & the d's are directories.

[harryray2]

It's showing in everything but definitely not finding it with a search. Although, if I do a search for test, everything finds it, but not if I search for test.

[JTB3]

David,
Have you seen this thread? Any comments
-JT

[void]

rename_trim fill fix this issue in the next alpha update.

Thanks for the issue report.

I will have an update soon.

I found it interesting that Windows Explorer doesn't handle multiple . and spaces:

Code: Select all

test . . . . .

[JTB3]

rename_trim fill fix this issue in the next alpha update.
Thanks for the issue report. I will have an update soon.
I found it interesting that Windows Explorer doesn't handle multiple . and spaces:

Thanks, and 'yes'