Before extract archive.7z, I always check what in side:
$ 7z l archive.7z
...SKIP...
2010-01-01 00:00:00 ..... 25856 7367 jsloader/resource/gre/modules/source-editor-textarea.jsm
2010-01-01 00:00:00 ..... 4656 1669 jsloader/resource/gre/modules/FileUtils.jsm
2010-01-01 00:00:00 ..... 1856 943 jsloader/resource/gre/modules/DownloadPaths.jsm
2010-01-01 00:00:00 ..... 7096 2724 jsloader/resource/gre/modules/CertUtils.jsm
2010-01-01 00:00:00 ..... 540 346 jsloader/resource/gre/modules/jsdebugger.jsm
2010-01-01 00:00:00 ..... 12964 4225 jsloader/resource/gre/modules/CommonDialog.jsm
2010-01-01 00:00:00 ..... 9692 3272 jsloader/resource/gre/modules/NetworkHelper.jsm
2010-01-01 00:00:00 ..... 11252 3503 jsloader/resource/gre/modules/AutocompletePopup.jsm
------------------- ----- ------------ ------------ ------------------------
17928547 5269642 1489 files, 0 folders
It will print a long message, if archive.7z contains a lot of files and dirs.
It's not very useful. Because I cannot see the overall structure of archive.7z.
Is is possible to print out a dir tree before extract it.
├── jsloader
│ └── resource
│ └── gre
│ ├── components
│ └── modules
│ ├── devtools
│ ├── services-crypto
│ ├── services-sync
│ │ ├── engines
│ │ └── ext
│ └── tabview
I use tree -d archive to get the tree after running 7z x archive.7z -oarchive.
If I can extract only the directories of archive.7z,
I can run tree -d archive ; rm -r archive to get the tree.