FreeCommander Forum

FreeCommander treats the very first dot in a filename as marker for file extension - not taking into account how many more dots there might be



If the user has a file named
then the FC sees it apparently as
And so this leads to a situation when if the user has extension-less files like
and uses Quick Filter code
then the results shown to the user will only reveal files
thus omitting And so a question arises- how is the user suppose to filter / find these with multiple dots?



This also breaks the modus operandi when such dotted files are worked on by the Multi Rename tool, because if the user decides to add extensions to such files and turn them to e.g. TXT files, then the result will be
instead of correct

So the rule should be for FC to look for the last dot in a FILENAME to treat is as the marker that splits the filename and its extension

As to my knowledge, there are no file extensions that have dots in them

I see no problem with such names in the current version of FC.
If you have the file then you have file with the extension '. something'.

The following string in Quick Filter is a special string for searching files without extension:

You can search for such files the same way as in Windows Explorer: No problem for Multi Rename too. If you want to add the .txt extension you should use in "File extension" field:

And by current version you mean current donor, and not public 861?

Because in 861 this works as I have described it

Marek wrote: 18.02.2022, 22:23 I see no problem with such names in the current version of FC.
[...]

I am sorry, but for me [currently in version 880 32-bit public] putting
into the box of Quick Filter just does not show extension-less files like

Forez wrote: 31.12.2022, 23:25

Marek wrote: 18.02.2022, 22:23 I see no problem with such names in the current version of FC.
[...]

I am sorry, but for me [currently in version 880 32-bit public]
[...]

And now also it does not work in versions:
● 880 64-bit Donor
● 885 64-bit Donor Portable

It works good here.

FC 880 32-bit public, 885 64-bit donor, Windows 10 21H1 64-bit.

Are you telling me that after downloading this archive https://ufile.io/6rr2psy1 and getting out of it file named >>Test... something<< and entering in the box of Quick Filter >>.*<< all you see in a Panel is only this file
>>Test... something<<?

Not with the steps from last post, but I think it works good, see the post above from Marek.

I see now, that I had initially misunderstood his answer

But despite it this discussion somewhat comes back now to the core issue - which is that

Forez wrote: 17.02.2022, 23:20 FreeCommander treats the very first dot in a filename as marker for file extension - not taking into account how many more dots there might be
[...]

which leads to issues described also in my initial post

So let me re-postulate:


I would like to suggest FC to start paying attention to how many dots a Filename has in it - and thus treat only the very last dot as separator of Filename from Extension instead of first dot. And also to give user a choice if [last] dot followed by a pause sign should be treated as the first sign of Extension - or if FC should assume that such file has no Extension at all. This rules should be applied thorough all elements / feature of FreeCommander

This will allow for finding through the Quick Filter of files like
[which are intended and viewed by user as extension-less] with unified method [applicable to truly extension-less files] and will also avert [for users dealing with such unusually named files] issues with bulk renaming of them with the Multi Rename tool

In other words: stop FC from seeing such file like the above example as
and let it see as
with better alternative of seeing it as

Forez wrote: 25.04.2023, 22:08 [....]
this discussion somewhat comes back now to the core issue - which is that

Forez wrote: 17.02.2022, 23:20 FreeCommander treats the very first dot in a filename as marker for file extension - not taking into account how many more dots there might be
[...]

I just realized that this is only half true


Because it is true for the Multi Rename feature, the Search ans also Quick Filter - but Panel has no issue with handling them in a more logical way. And that is because if a user has chosen option

Tools > Settings > File/folder operations > Select only filename

and attempts in a Panel to rename a file like e.g.
then FC selects the whole
and not just

So current behavior is also inconsistent - thus once again: please make Muti Rename and other features of FC always look for the last dot and treat it as delimiter between filename and its extension; while also treating a pause after last dot as indication of the file not having extension at all but only filename

There is also this issue with how last dot in a filename is not being treated as the separator from extension: https://freecommander.com/forum/viewtopic.php?t=8505