FileName Extension Bug

[Rynsrod]

I was Create Text File from TC with hot Keys Ctrl+F4 and give name just "123".
I use FAR as external file editor like that and invoke them as follows:
"FAR\far.exe" /e "%1"

As a result I have 2 file on disk:

Code: Select all

123 ( with Zero FileSize),
123. (123[dot]) (with my file size)

After that I can't delete second file by Nothing.
Only FAR could remove it.

I not sure maybe this is Bug of Far but I didn't find this problem before TC7.5 and higher.

Thank you for attention.

[MVV]

That's strange because in Windows names "123" and "123." are the same! So they must point to one file. Maybe your FAR made that file and kept it opened so no one else couldn't remove it?

[Rynsrod]

That's strange because in Windows names "123" and "123." are the same! So they must point to one file. Maybe your FAR made that file and kept it opened so no one else couldn't remove it?

That is really strange but when I try to remove this TC says
"File C:\123. not found!"

[DrShark]

That's strange because in Windows names "123" and "123." are the same! So they must point to one file. Maybe your FAR made that file and kept it opened so no one else couldn't remove it?

FAR has some workarounds especially to remove such a wrong names like this.
You can read here (in russian) that FAR is a one of suggested tools for such cases.

[MVV]

Well, it seems that TC on Shift+F4 created file 123 and passed name to editor, and FAR created file really with dot in name. It is strange why FAR created a file with dot in name when you ask for edit file without it.

BTW as I see TC passes to editor name with dot at the end (maybe to indicate that file have no extension). Anyway it is a FAR bug that it created file with dot in the name instead of creating just file without extension.

You can read here (in russian) that FAR is a one of suggested tools for such cases.

Thanks for info but here FAR made this buggy name instead of just opening empty existing file:) "Сам наломал дров - сам пусть и расхлебывает=))"

Anyway there is a way to create/rename/delete such buggy files. In NT systems special prefix "\\?" exists that should be placed before file/folder path for names longer than 260 characters. The joke is that if you pass such name, OS doesn't clear it from spaces etc so you may easilly create such non-deleteable file using simple command:

Code: Select all

echo Hello>"\\?\C:\123."

In this case dot will be really written into filename. And no app will work with such filename if it doesn't use prefix "\\?" or just removes extra dots at the end of name.

To delete such file you may use console command:

Code: Select all

del "\\?\C:\123."

[DrShark]

You can read here (in russian) that FAR is a one of suggested tools for such cases.

Thanks for info but here FAR made this buggy name instead of just opening empty existing file:) "Сам наломал дров - сам пусть и расхлебывает=))"

About FAR bug I have to agree and Rynsrod have to contact to FAR Team regarding it.

My post is about a Total Commander-related problem: it cannot remove a buggy-named file while another file manager can.

[ghisler(Author)]

It seems like FAR is using its hack (probably via \\?\ prefix) to create a name with trailing dot.

So why does TC pass "123." to the program and not "123"? It's for Notepad: If you pass "123" to notepad, it will create a file "123.txt" instead of opening "123".

Therefore I cannot change the current behaviour, sorry.