XYplorer Beta Club

For eg: If I have a file named "xyplorer_6.80.0026_beta_noinstall" and i set an extension say "zip", then anything after the last "." is suffixed with zip and I get "xyplorer_6.80.zip".
If i am right, most extensions are between 2-3 characters (atleast de facto) in length. So is it possible that while renaming XY does NOT trim the filename, if the period (.) is more than 3 characters away from the file ending?
Ofcourse, this is a really tiny issue. Just reporting.

Perhaps instead of length based, it could attempt to see if the file has a registered extension.

If it does, replace it, otherwise append the new one.

TheQwerty wrote:Perhaps instead of length based, it could attempt to see if the file has a registered extension.

If it does, replace it, otherwise append the new one.

I'll vote for that as well.

ugus wrote:

TheQwerty wrote:Perhaps instead of length based, it could attempt to see if the file has a registered extension.

If it does, replace it, otherwise append the new one.

I'll vote for that as well.

I don't think I do. I'm not sure this is an ideal solution. Might be a case of smart thinking from the app I do not like. For starter, I do use non-registered extension often and consider them as "valid" extension (even though they're not registered, or longer than 3 characters) ; and I would suspect this might require some time to scan all registered extensions, and I don't want that whenever I use a simple rename Set Extension command !

I'm with jacky on this one! I've used nonstandard extensions on occasion...But I do also agree with original issue...so...???
BTW, a common registered extension is .HTML which is 4 chars...

jacky wrote:

ugus wrote:

TheQwerty wrote:Perhaps instead of length based, it could attempt to see if the file has a registered extension.

If it does, replace it, otherwise append the new one.

I'll vote for that as well.

I don't think I do. I'm not sure this is an ideal solution. Might be a case of smart thinking from the app I do not like. For starter, I do use non-registered extension often and consider them as "valid" extension (even though they're not registered, or longer than 3 characters) ; and I would suspect this might require some time to scan all registered extensions, and I don't want that whenever I use a simple rename Set Extension command !

What if in addition to the registered extensions check there was also an internal list of XY-registered extensions which the user could use to store non-registered but known extensions and XY could check this list first?


My feelings are if it's not a registered extension then XY can't be sure that it is the extension and thus shouldn't be changing it. If I want to force the change regardless of valid extensions I can do so with regular expressions (or batch rename for that matter).

Some of the non-std extensions that I've used are temporary one-time only things, so having it detect only "officially" registered ext's would be sufficient, IMO...and I don't think it would take THAT long XY to do that lookup.

Plus, if I using this command, I have to select the files I want it to operate on, so some of the blame has to come back to me if I get one misnamed.

Addendum/Upd: When XY finds a name that has more than 4 chars after last ".", it is more than likely not an extension but part of name, and thus the file doesn't presently have an extension, which is, IMO, quite rare, so I'm beginning to think this is a user error rather than XY.