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
Sometimes it can be helpful. In particular, I just experienced a problem with extracted script not having an executable bit set, which I almost deemed to be a bug in lxqt-archiver, but then I figured it's that the original archive didn't have it for some reason. Being able to look at file permissions inside an archive would've helped.
For example, here's what the column looks like for ark:
Latest lxqt-archiver, built from commit 5fbc6f7 only has these:
The text was updated successfully, but these errors were encountered:
lxqt-archiver gets its core from the GLib-based code of file-roller/engrampa. I didn't find a permission column in engrampa.
Showing permissions should be possible with some archive formats but I don't know how easy or difficult its implementation is -- if the core doesn't support it, the job might not be easy.
Sometimes it can be helpful. In particular, I just experienced a problem with extracted script not having an executable bit set, which I almost deemed to be a bug in lxqt-archiver, but then I figured it's that the original archive didn't have it for some reason. Being able to look at file permissions inside an archive would've helped.
For example, here's what the column looks like for ark:
Latest lxqt-archiver, built from commit 5fbc6f7 only has these:
The text was updated successfully, but these errors were encountered: