To reproduce:
1. On Windows 7, browse using TC 8.0x (32 or 64-bit) to an archive file (zip, rar, etc.),
2. Select a single inner file for unpacking,
3. At the 'Unpack selected 1 file(s) to:' dialog, extend the default path with a file name such as 'abc.txt' (without any trailing slashes),
4. Click 'Ok'.
Result:
A (redundant) directory is created in the target pane's path, having the name 'abc.txt'. Inside the newly created directory resides the unpacked file, with its original name instead of the name that was typed in step (3).
Unpacking files creates a redundant directory
Moderators: Hacker, petermad, Stefan2, white
-
- Junior Member
- Posts: 7
- Joined: 2009-10-24, 08:57 UTC
-
- Junior Member
- Posts: 7
- Joined: 2009-10-24, 08:57 UTC
You're right, thank you.
I ran into this while extracting a file from an archive to a directory having a file with the same name. In order to prevent a potential overwrite, I tried renaming the file before the conflict actually occurred.
The 'Overwrite/Rename' dialog works as expected, and the dialog we discussed says 'Unpack... to', not 'Unpack... as', so it's probably OK.
I rechecked with an older TC version and the behavior was the same.
I ran into this while extracting a file from an archive to a directory having a file with the same name. In order to prevent a potential overwrite, I tried renaming the file before the conflict actually occurred.
The 'Overwrite/Rename' dialog works as expected, and the dialog we discussed says 'Unpack... to', not 'Unpack... as', so it's probably OK.
I rechecked with an older TC version and the behavior was the same.