You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a folder which is to be extracted already exists, the number appended to the folder name starts at 3, not 2.
This was working correctly quite a while ago, but I'm not sure exactly what version of Keka broke it.
To Reproduce
Steps to reproduce the behavior:
Extract an archive which creates a folder, say, "folder"
Extract the same archive again to the same folder
Observe that the resulting folder is named "folder 3" instead of "folder 2"
Expected behavior
The resulting folder is named "folder 2".
Additional context
Keka has Full Disk Access permissions.
The text was updated successfully, but these errors were encountered:
OnesuchDev
changed the title
[BUG] If a folder which is to be extracted already exists, the resulting folder is renamed to end with 3 instead of 2
[BUG] If a folder which is to be extracted already exists, the number appended to the folder name starts at 3, not 2
Oct 24, 2024
Thanks @OnesuchDev. Checked this out and turns out it's like this since v1.3.0 (06/2023), worked properly in v1.2.61. The bug was introduced since there was a redesign of the naming code in this v1.3.0 change:
Enhanced extraction naming with multiple extensions
Sadly just released v1.4.5 so this fix will be available in a few weeks since it is not critical.
Configuration
Describe the bug
If a folder which is to be extracted already exists, the number appended to the folder name starts at 3, not 2.
This was working correctly quite a while ago, but I'm not sure exactly what version of Keka broke it.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The resulting folder is named "folder 2".
Additional context
Keka has Full Disk Access permissions.
The text was updated successfully, but these errors were encountered: