Crashes on Linux x86_64

[kseistrup]

Virex-Canopy built from commit d963d44 crashes on Linux:

$ env RUST_BACKTRACE=full target/release/virex-canopy . --depth 2
╔══════════════════════════╗
║   Welcome to Virex-Canopy!   ║
╚══════════════════════════╝

Your directory tree visualizer is ready to go!

Commands:
  [x] virex-canopy <PATH>       Show tree for a folder
  [x] --depth <N>               Limit tree depth
  [x] --hidden                  Include hidden files
  [x] --json                    Export tree as JSON
  [x] --help                    Show this message
  [x] --interactive             Enable interactive TUI mode
  [x] --filter <PATTERN>        Filter files with glob pattern, e.g. *.rs
  [x] --test-colors             Test color output
  [x] --check-path              Check if exe is in PATH

Tip: Try `virex-canox86_64py . --depth 2` to explore your current folder!

thread 'main' (3104788) panicked at src/main.rs:161:48:
called `Result::unwrap()` on an `Err` value: NotPresent
stack backtrace:
   0:     0x5581579473c2 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hf7863edf5bd3fe9c
   1:     0x558157958c5f - core::fmt::write::h2dc8094dee4c3081
   2:     0x558157918711 - std::io::Write::write_fmt::h475f3c199917f803
   3:     0x558157923d22 - std::sys::backtrace::BacktraceLock::print::hda2f5b161b33c01d
   4:     0x55815792667f - std::panicking::default_hook::{{closure}}::h8957870b453bd595
   5:     0x5581579264d9 - std::panicking::default_hook::hf3d9a7b1cdb74722
   6:     0x558157926d05 - std::panicking::panic_with_hook::h011a155645fbd86e
   7:     0x558157926b9a - std::panicking::panic_handler::{{closure}}::h55a4680715609b11
   8:     0x558157923e59 - std::sys::backtrace::__rust_end_short_backtrace::h5a0c9848a87e1635
   9:     0x55815790ce0d - __rustc[1c8c0b0c56d5ad47]::rust_begin_unwind
  10:     0x558157961e30 - core::panicking::panic_fmt::ha9e78b3b184ec3c5
  11:     0x558157961156 - core::result::unwrap_failed::h9df0bea10b4dc845
  12:     0x558157878b87 - virex_canopy::main::hbed279a39c0127cc
  13:     0x55815788ec93 - std::sys::backtrace::__rust_begin_short_backtrace::h4e396c8bdcb388c5
  14:     0x5581578915d9 - std::rt::lang_start::{{closure}}::he66a4962390220d2
  15:     0x55815791a330 - std::rt::lang_start_internal::h8b234057c0366d1f
  16:     0x558157880185 - main
  17:     0x7f64ee427675 - <unknown>
  18:     0x7f64ee427729 - __libc_start_main
  19:     0x558157871815 - _start
  20:                0x0 - <unknown>

It takes quite some time (~4 seconds) before anything happens at all, then it crashes. It is invoked from within its own git repo, so it's not like it has a gazilion files and directories to tally.

Also, the initial “banner” is misaligned, but that is a minor issue.

Also, a -V or --version switch would be nice to have.

Also, a screenshot of how it is supposed to look would be nice as an appetizer.

Cheers.

---

$ cargo --version
cargo 1.91.1 (ea2d97820 2025-10-10) (Arch Linux rust 1:1.91.1-2)

---

Edit: typo

[kseistrup]

Ah, the executale demands an environment variable, $APPDATA, where it can install itself to and keep its log:

$ mkdir appdata
$ env APPDATA=$(pwd)/appdata RUST_BACKTRACE=full target/release/virex-canopy . --depth 2
╔══════════════════════════╗
║   Welcome to Virex-Canopy!   ║
╚══════════════════════════╝

Your directory tree visualizer is ready to go!

Commands:
  [x] virex-canopy <PATH>       Show tree for a folder
  [x] --depth <N>               Limit tree depth
  [x] --hidden                  Include hidden files
  [x] --json                    Export tree as JSON
  [x] --help                    Show this message
  [x] --interactive             Enable interactive TUI mode
  [x] --filter <PATTERN>        Filter files with glob pattern, e.g. *.rs
  [x] --test-colors             Test color output
  [x] --check-path              Check if exe is in PATH

Tip: Try `virex-canopy . --depth 2` to explore your current folder!
.
└── [DIR] 
    ├── [lock] Cargo.lock (23.1K)
    ├── [toml] Cargo.toml (639B)
    ├── [FILE] LICENSE (34.3K)
    ├── [.md] README.md (1.8K)
    ├── [DIR] appdata
    │   ├── [EXEC] canopy.exe (1.7M)
    │   └── [log] canopy.log (58B)
    ├── [DIR] installer
    │   ├── [lock] Cargo.lock (160B)
    │   ├── [toml] Cargo.toml (87B)
    │   ├── [.rs] build.rs (659B)
    │   └── [DIR] src
    │       └── [.rs] main.rs (38.1K)
    ├── [DIR] src
    │   └── [.rs] main.rs (20.4K)
    └── [DIR] target
        ├── [tag] CACHEDIR.TAG (177B)
        └── [DIR] release
            ├── [DIR] build
            ├── [DIR] deps
            ├── [DIR] examples
            ├── [DIR] incremental
            ├── [FILE] virex-canopy (1.7M)
            └── [d] virex-canopy.d (77B)
$ ls -la appdata
.rwxr-xr-x 1.783.464 kas 13 Nov 13:16 canopy.exe
.rw-r--r--        58 kas 13 Nov 13:16 canopy.log

Sorry, but that's not how things work on Linux.

Even with the executable in the “appdata” directory, it still takes 4 full seconds to print anything.