voidtools forum

Fixed for the next alpha update.

Thank you for the bug report.

Everything 1.5.0.1270a fixes an issue with the newly generated filename from a rename collision.

void wrote: ↑Tue Jul 27, 2021 7:23 am Everything 1.5.0.1270a fixes an issue with the newly generated filename from a rename collision.

This is what happens when I click yes.

I can rename a file >340 characters without any problem,
i.e. in my opinion there must be a problem with the file name.

Naming Files, Paths, and Namespaces -> Naming Conventions 
 
____________________________________________________________________________
Windows 10 Pro (x64) Version 21H1 (OS build 19043.1151) | 'Everything' 1.5.0.1270a (x64)

tuska wrote: ↑Sun Aug 01, 2021 1:58 pm I can rename a file >340 characters without any problem,
i.e. in my opinion there must be a problem with the file name.

____________________________________________________________________________
Windows 10 Pro (x64) Version 21H1 (OS build 19043.1151) | 'Everything' 1.5.0.1270a (x64)

This is the video capture, I'm not lying. The file name is 1.pdf.

- What is your total path length? (path + filename)
- Which Everything version?
- Which Windows version?

tuska wrote: ↑Sun Aug 01, 2021 2:16 pm What is your total path length? (path + filename)

D:\Downloads\1.pdf
V1.5.0.1270a (x64)
Windows 11 x64 22000.100

Thank you!

You are already using Windows 11 - probably that is the problem...

tuska wrote: ↑Sun Aug 01, 2021 2:21 pm Thank you!

The .ZIP file contains the file bandicam.mp4

You are already using Windows 11 - probably that is the problem...

I absolutely hate windows 11, regretted the minute I upgraded.

Thanks anyway.

I can confirm this error.

I have only just watched the video more closely.

When renaming, Everything tells you the following:

Do you want to rename "2.pdf" to "1 (2).pdf"?

After clicking on the "Yes" button, the file should be renamed to "1 (2).pdf".
However, this does not happen, instead, the error message appears.

Indeed!

tuska wrote: ↑Sun Aug 01, 2021 2:36 pm I have only just watched the video more closely.

When renaming, Everything tells you the following:

Do you want to rename "2.pdf" to "1 (2).pdf"?

After clicking on the "Yes" button, the file should be renamed to "1 (2).pdf".
However, this does not happen, instead, the error message appears.

Windows 11 didn't cause this problem. Because I still experience this after I reinstalled windows 10.

Have you tried zipping the file?

Whats happened to me on several occasions is that I've copied and pasted a file name and got the illegal character message. I found that zipping it up and typing the filename of the newly compressed file works.

I use Win 7.

The other way I found was to copy the file and rename the copy but type the name in manually, don't paste it.

775405984 wrote: ↑Sun Aug 01, 2021 6:20 pm Windows 11 didn't cause this problem.

Yes, you are right and unfortunately I was wrong (I wrongly suspected Windows 11 as the originator).

After that, however, the user ovg and I realized almost at the same time that the fault is with Everything.

____________________________________________________________________________
Windows 10 Pro (x64) Version 21H1 (OS build 19043.1151) | 'Everything' 1.5.0.1270a (x64)

I use a file copying programme which overrides Windows and when it finds a conflict it gives me the option to overwrite or keep both versions of the file.
It also verifies the file.

harryray2 wrote: ↑Sun Aug 01, 2021 6:36 pm I use a file copying programme which overrides Windows and when it finds a conflict
it gives me the option to overwrite or keep both versions of the file.
It also verifies the file.

Yes, but that's not what this topic is about.
This is a bug report that has now been confirmed by 2 other users.

Yes, sorry, I got distracted while reading the post...

I am working on a fix..

Thank you for the bug report.

related: Rename with Overwrite situation drops renamed file into instalDir

Everything 1.5.0.1271a fixes an issue with the generated new filename from a rename collision.

Everything was not including the full path with the newly generated filename.

Thanks for fixing, it's working fine now.

I can also confirm the bugfix in Everything 1.5.0.1271a (x64) and (x86).
Thank you!