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
After extracting a file and realizing that the same file exists at the same directory, Engrampa would ask if we might replace the file or if we might rename the new extracted file. (File-roller and Ark do this)
Actual behaviour
Engrampa - after extracting an file that meets another file with same name/extension at the same directory - just generates a another version of the file, like: "file.txt", "file.txt(2), file.txt(3)
Steps to reproduce the behaviour
Compress TEXT.txt file inside a PACK.7z. So, at the same directory we have TEXT.txt and PACK.7z. Just extract PACK.7z there. Engrampa just generates TEXT.txt(2). The Expected is to be asked if the user wants to replace the existing file or rename the new extracted file.
MATE general version
1.18
Package version
Linux Distribution
Debian 9, Ubuntu 16.04, Mint 18.3
Link to downstream report of your Distribution
The text was updated successfully, but these errors were encountered:
Expected behaviour
After extracting a file and realizing that the same file exists at the same directory, Engrampa would ask if we might replace the file or if we might rename the new extracted file. (File-roller and Ark do this)
Actual behaviour
Engrampa - after extracting an file that meets another file with same name/extension at the same directory - just generates a another version of the file, like: "file.txt", "file.txt(2), file.txt(3)
Steps to reproduce the behaviour
Compress TEXT.txt file inside a PACK.7z. So, at the same directory we have TEXT.txt and PACK.7z. Just extract PACK.7z there. Engrampa just generates TEXT.txt(2). The Expected is to be asked if the user wants to replace the existing file or rename the new extracted file.
MATE general version
1.18
Package version
Linux Distribution
Debian 9, Ubuntu 16.04, Mint 18.3
Link to downstream report of your Distribution
The text was updated successfully, but these errors were encountered: