Any opinions on the Nautilus automatic decompression behavior? decompressing all archives by default when you only want to open a file inside of it, Making people by mistake extract the archive multiple times every time they open it?
I noticed by mistake the new change when I opened Zip file and noticed no changes (didn't noticed the folder was already extracted every time I tried) and got a folder full of garbage temporary extractions.
On Wed, 2016-12-21 at 10:59 -0400, Robert Marcano wrote:
Any opinions on the Nautilus automatic decompression behavior? decompressing all archives by default when you only want to open a file inside of it, Making people by mistake extract the archive multiple times every time they open it?
I noticed by mistake the new change when I opened Zip file and noticed no changes (didn't noticed the folder was already extracted every time I tried) and got a folder full of garbage temporary extractions.
This has happened to me too. I'm glad we have real support for compressed archives in nautilus now, but I agree it would be better to not extract stuff automatically. Nautilus should just show the user inside the archive, similar to what Windows Explorer does, and only perform extraction when explicitly requested.
Michael
On 12/21/2016 10:58 AM, Michael Catanzaro wrote:
This has happened to me too. I'm glad we have real support for compressed archives in nautilus now, but I agree it would be better to not extract stuff automatically. Nautilus should just show the user inside the archive, similar to what Windows Explorer does, and only perform extraction when explicitly requested.
I consider the changes on the compression side a regression. The previous window allowed a handful of file types, but the new window only gives you 3 choices. I still deal with Linux distros that are pre-xz so removing a tar.gz option is a downgrade.
Michael or Robert, if one of you decide to file a bug or open a discussion upstream please let us know so I can CC on it.
Thanks, Michael
On 2016-12-21 18:29, Michael Cronenworth wrote:
On 12/21/2016 10:58 AM, Michael Catanzaro wrote:
This has happened to me too. I'm glad we have real support for compressed archives in nautilus now, but I agree it would be better to not extract stuff automatically. Nautilus should just show the user inside the archive, similar to what Windows Explorer does, and only perform extraction when explicitly requested.
I consider the changes on the compression side a regression. The previous window allowed a handful of file types, but the new window only gives you 3 choices. I still deal with Linux distros that are pre-xz so removing a tar.gz option is a downgrade.
Michael or Robert, if one of you decide to file a bug or open a discussion upstream please let us know so I can CC on it.
Isn't this available if you launch file-roller from the shell though? (if file-roller is installed by default still, I'm unsure, since I upgraded from F24 instead of doing a fresh install) - Andreas
On 12/21/2016 11:36 AM, Andreas Nilsson wrote:
Isn't this available if you launch file-roller from the shell though? (if file-roller is installed by default still, I'm unsure, since I upgraded from F24 instead of doing a fresh install)
Yes, but that's a few extra keystrokes. What was wrong with the old nautilus UI and behavior?
There's no exact one right way to do this. Windows shows the archive as if it were a directory. Whereas macOS decompresses the whole archive to its own directory. Still another option would be decompressing the archive into its own directory and then moving the archive into the local user trash directory. It's just a matter of what you're used to, so the real issue is merely that the behavior has changed, rather than it's inherently incorrect behavior.
Chris Murphy
On 12/21/2016 05:05 PM, Chris Murphy wrote:
There's no exact one right way to do this. Windows shows the archive as if it were a directory. Whereas macOS decompresses the whole archive to its own directory. Still another option would be decompressing the archive into its own directory and then moving the archive into the local user trash directory. It's just a matter of what you're used to, so the real issue is merely that the behavior has changed, rather than it's inherently incorrect behavior.
IMHO decompressing by default is a bad behavior, what about big archives and you only want to check the contents? what about if the user just created a new archive and want to check y everything needed is inside? another decompressed copy? the archive removed when the user just created it
I think the more user friendly solution is for gvfs to have a archive filesystem so users are able to use files like they are part of the real filesystem (via gvfs fuse integration), Instead of decompressing all files every time the user decide to browse the contents.
Chris Murphy _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org
desktop@lists.fedoraproject.org