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
Is your feature request related to a problem? Please describe
I'm using the Mac version, currently in MacOS 10.11.
I've discovered the xz/txz format thanks to Keka, but for some unknown reason, txz has been replaced by tar.xz after a while.
txz is natively supported by MacOS, which makes it a format of choice. I see that renaming tar.xz files to txz works, so why bother with a double-extension?
Describe the solution you'd like
Allow the user to choose between txz and tar.xz, preferably in the prefs — or when saving a file.
Describe alternatives you've considered
• changing the extension to txz when saving a file, but it doesn't work.
• Renaming tar.xz files to txz in the Finder. But that makes an additional boring step.
Additional context
All the other compression tools I've tried support txz, so why bother with tar.xz if not for compatibility reasons?
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
I'm using the Mac version, currently in MacOS 10.11.
I've discovered the xz/txz format thanks to Keka, but for some unknown reason, txz has been replaced by tar.xz after a while.
txz is natively supported by MacOS, which makes it a format of choice. I see that renaming tar.xz files to txz works, so why bother with a double-extension?
Describe the solution you'd like
Allow the user to choose between txz and tar.xz, preferably in the prefs — or when saving a file.
Describe alternatives you've considered
• changing the extension to txz when saving a file, but it doesn't work.
• Renaming tar.xz files to txz in the Finder. But that makes an additional boring step.
Additional context
All the other compression tools I've tried support txz, so why bother with tar.xz if not for compatibility reasons?
The text was updated successfully, but these errors were encountered: