When running nat on a directory the user does not have access to, a rust error occurs instead of a soft app error such as a simple "permission denied". For example:

~ natls /path/that/I/dont/have/access/to
thread 'main' panicked at 'Failed to run natls: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }', src/main.rs:443:8
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I would expect it to throw a soft and less "intimidating" error such as:

~ ls /path/that/I/dont/have/access/to
ls: /path/that/I/dont/have/access/to: Permission denied

See below:

# davised @ vader in ~/.local/downloads [22:58:17]
$ natls --version
natls 2.1.8

# davised @ vader in ~/.local/downloads [22:56:28]
$ natls -lg
drwxr-xr-x     4 KB davised davised 00 000 00:00:00 cutadapt-3.1/
drwxr-xr-x     4 KB davised davised 00 000 00:00:00 ncbi-datasets-pylib-10.1.3/
drwxr-xr-x     4 KB davised davised 00 000 00:00:00 iqtree-2.0.6-Linux/
drwxr-xr-x     4 KB davised davised 00 000 00:00:00 iqtree-2.1.1-Linux/
...

The issue

The current release on snap does not match the actual version.

Reproduce

• install via "sudo snap install natls"
• check version of nat with "natls --version"

Things I tried

• update nat with "sudo snap refresh natls"

Idea for a fix

Snap should be integrated into a CI like GitHub Actions, Jenkins or similar to automatically update the binary. Or on each release someone should update the binary manually.

Hi,

It's good that you updated the README.md for a fresh look. As a user not knowing what natls does, it's not clear what it is, what it does fix and what it's written in (rust) and why.

Maybe add in the first sentence under the title what natls (an alternative to ls with colors written in rust, being superfast!) or something like that. Maybe add some speed test benchmark natls vs ls and lsd and exa

You have to sell this program a bit if you want people to use it. Why do they want to use it? :)

Also, maybe give some examples: natls -l -m shows what the screenshot does, I believe Anyways what do you think?

System Information:

• macOS Big Sur 11.1

• MacBook Pro (15-inch, 2018)

• nat version 2.1.10 (installed via Homebrew)

Sequence of commands:

export RUST_BACKTRACE=full To give full details about the crash

natls
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/utils/get_group.rs:6:8
stack backtrace:
   0:        0x10092860e - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h3b6ed74a60c4de30
   1:        0x1009576ae - core::fmt::write::h72dd6ddbc116ef3c
   2:        0x100927d1a - std::io::Write::write_fmt::h033803ce14d847cc
   3:        0x10093bb99 - std::panicking::default_hook::{{closure}}::h040276b51a1a4749
   4:        0x10093b8be - std::panicking::default_hook::h2a43ed83163cecb9
   5:        0x10093c12a - std::panicking::rust_panic_with_hook::h15f3dba6c099e04e
   6:        0x100928c99 - std::panicking::begin_panic_handler::{{closure}}::h33fb39231ad9a88d
   7:        0x100928788 - std::sys_common::backtrace::__rust_end_short_backtrace::hd5ec6f84e4df1d34
   8:        0x10093bca3 - _rust_begin_unwind
   9:        0x10095c9cf - core::panicking::panic_fmt::h7889f3b8e7c118f7
  10:        0x10095c927 - core::panicking::panic::h467f1ca176190211
  11:        0x1008be832 - natls::utils::get_group::group::hd7e992d1d04d532e
  12:        0x1008b9ee1 - natls::File::new::h1bc60eb99da8151d
  13:        0x1008c4ade - <core::iter::adapters::ResultShunt<I,E> as core::iter::traits::iterator::Iterator>::next::h724542ea187dcaf1
  14:        0x1008c15be - <alloc::vec::Vec<T> as alloc::vec::SpecFromIter<T,I>>::from_iter::hc2fbc564bc446f30
  15:        0x1008c4f42 - core::iter::adapters::process_results::h67eaf86eb83e6497
  16:        0x1008bb201 - natls::main::h7b891e1e5baa18b7
  17:        0x1008bcada - std::sys_common::backtrace::__rust_begin_short_backtrace::ha85bf5dbd5f6fb8d
  18:        0x1008bcafc - std::rt::lang_start::{{closure}}::he35549e67e86e1ef
  19:        0x10093f22e - std::rt::lang_start_internal::h1881ffd15d3416e4
  20:        0x1008bcaa9 - _main

:information_source: The other nat commands work just fine. The issue happens only with the regular execution, without any parameters.

Nice little tool!

I was wondering about the possibility of alphabetising files and folders

As you can see the files are not ordered which can make it a little cumbersome to use

Thanks.

It can not list fs root "/"

$ nat /
Error: Os { code: 2, kind: NotFound, message: "No such file or directory" }

but

$ ls /
Applications	Library		Users		bin		dev		home		private		tmp		var
EFI-Backups	System		Volumes		cores		etc		opt		sbin		usr

This is on OS X 10.15

My Ubuntu rust packages are probably quite old. But I don't think it matters too much.

tilmanb@zuse:~/git/nat$ RUST_BACKTRACE=1 cargo run
    Finished dev [unoptimized + debuginfo] target(s) in 0.07s
     Running `target/debug/nat`
thread 'main' panicked at 'attempt to subtract with overflow', src/main.rs:76:15
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /usr/src/rustc-1.43.0/vendor/backtrace/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /usr/src/rustc-1.43.0/vendor/backtrace/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1063
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1426
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:204
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:224
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:470
  11: rust_begin_unwind
             at src/libstd/panicking.rs:378
  12: core::panicking::panic_fmt
             at src/libcore/panicking.rs:85
  13: core::panicking::panic
             at src/libcore/panicking.rs:52
  14: nat::main
             at src/main.rs:76
  15: std::rt::lang_start::{{closure}}
             at /usr/src/rustc-1.43.0/src/libstd/rt.rs:67
  16: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:52
  17: std::panicking::try::do_call
             at src/libstd/panicking.rs:303
  18: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:86
  19: std::panicking::try
             at src/libstd/panicking.rs:281
  20: std::panic::catch_unwind
             at src/libstd/panic.rs:394
  21: std::rt::lang_start_internal
             at src/libstd/rt.rs:51
  22: std::rt::lang_start
             at /usr/src/rustc-1.43.0/src/libstd/rt.rs:67
  23: main
  24: __libc_start_main
  25: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
permissions   size      last modified       grouptilmanb@zuse:~/git/nat$

tilmanb@zuse:~/git/nat$ git log -n 1
commit 6d34b3c80b77f94e2f076158affcb8e6ba8d9b04 (HEAD -> main, origin/main, origin/HEAD)
Author: Will Lane <[email protected]>
Date:   Fri Oct 23 00:29:00 2020 -0700

    updated colors for users using lighter terminal themes

tilmanb@zuse:~/git/nat$ rustc --version
rustc 1.43.0

My rust foo is very weak and I didn't have tome to dig into it. But perhaps you want to know.

Feel free to just close the ticket.

OS: macOS 11.1 shell: zsh Terminal: Default Application source: Homebrew Cargo version: 1.49.0

Running natls nonexistent_file returns the following error:

thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/utils/get_group.rs:5:53

This is an unusual use case, but sometimes I want to see large files being copied and their size growing.

I'd love to use watch natls for those times.

The tool does not work for me. Downloaded and put into /usr/local/bin and changed permissions to 755 When I run it, it just puts lines on my screen. I am using macOS 10.15.7