Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ZIP-archive and directory sorting is broken. #950

Open
TpaBkaY opened this issue Jan 13, 2025 · 1 comment
Open

ZIP-archive and directory sorting is broken. #950

TpaBkaY opened this issue Jan 13, 2025 · 1 comment

Comments

@TpaBkaY
Copy link
Contributor

TpaBkaY commented Jan 13, 2025

@okdana What is the main idea to roll back these changes? What problem does it fix?

Originally posted by @TpaBkaY in 1017633

@okdana
Copy link
Contributor

okdana commented Jan 13, 2025

hi @TpaBkaY. like i mentioned in #943, the mister menu treats zip archives almost exactly like directories for the purposes of navigation, so it kind of pressures you to do the same. which i have been for the last 5 years

the particular use case i have that the previous change broke is a file structure like this:

1 rarely updated files.zip
2 frequently updated files/
3 rarely updated files.zip
1 regular file.bin

with the previous change it became:

2 frequently updated files/
1 rarely updated files.zip
3 rarely updated files.zip
1 regular file.bin

which seems like 'the worst of both worlds' to me

besides breaking my particular habits it just doesn't seem useful -- what benefit does sorting zip files separately from other files and directories provide? it's not a file manager, the only thing you can do is navigate, and again zips are exactly the same as directories for that purpose. so why distinguish them? is there another use case i don't understand?

i mentioned in #943 that i would personally prefer that zips get treated just like any other file, and that they automatically select a file inside if it's the only one there. this is similar to how many software emulators behave. if there was an ini setting to toggle between that and the current behaviour (and maybe the one from your previous change? if it's actually a common use case?) i think that could make everyone happy. but i had the feeling that sorgelig prefers not to add lots of ini settings so i made the less drastic change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants