One solution could be to use the docker version of vhs, and edit the dockerfile to pull your desired font.

I&#x27;ve seen a lot of people use asciinema to record and share terminal recordings, it works quite well

lol good catch, and I totally missed itI used vhs to record the gif which must not run the script in my native terminal! I’ll have to see about fixing it!

I didn&#x27;t notice, I was too busy seeing how impressive and useful this tool is.And with fuzzy matching built in? Just amazing. Good job OP.

Seems quite cool! Though the demo gif with (what seem to be?) broken icons is a bold choice :p

crazy good, so it&#x27;ll ignore showing files enlisted in gitignore while listing?

No offense, but 4.3MB is huge for what it does. Most shells take less space than that! Where&#x27;s all the bloat coming from?

&gt; The binary is also 53MThat&#x27;s a debug binary, and the vast majority of that is debug symbols. A release build of this project is 4.3M, an order of magnitude smaller.Also, compiling out the default features of the git2 crate eliminates several dependencies and reduces it further to 3.6M.<a href="https:&#x2F;&#x2F;github.com&#x2F;bgreenwell&#x2F;lstr&#x2F;pull&#x2F;5">https:&#x2F;&#x2F;github.com&#x2F;bgreenwell&#x2F;lstr&#x2F;pull&#x2F;5</a><a href="https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;git2-rs&#x2F;pull&#x2F;1168">https:&#x2F;&#x2F;github.com&#x2F;rust-lang&#x2F;git2-rs&#x2F;pull&#x2F;1168</a>Stripping the binary further improves it to 2.9M, and some further optimizations get it to 2.2M without any compromise to performance. (You can get it smaller by optimizing for size, but I wouldn&#x27;t recommend that unless you really do value size more than performance.)

Likely needs features tuned. I compared Eza, similarly in Rust, and it&#x27;s 1.6 MiB compiled. Looking at the Cargo.toml, it includes git2 with default-features = false. <a href="https:&#x2F;&#x2F;github.com&#x2F;eza-community&#x2F;eza&#x2F;blob&#x2F;main&#x2F;Cargo.toml">https:&#x2F;&#x2F;github.com&#x2F;eza-community&#x2F;eza&#x2F;blob&#x2F;main&#x2F;Cargo.toml</a>

I did some benchmarks on one of our CLI and found that `opt-level = &quot;z&quot;` reduced the size from 2.68M to 2.28M, and shaved 10% on the build time, worth a try.I&#x27;ll try with `panic = &quot;abort&quot;` for our next release, thanks for the reminder.

Building in release:<pre><code> cargo build --release
 du -sh .&#x2F;target&#x2F;release&#x2F;lstr -&gt; 4.4M
</code></pre>
Building with other release options brings it down to 2.3M:<pre><code> [profile.release]
 codegen-units = 1
 opt-level = &quot;s&quot;
 lto = true
 panic = &quot;abort&quot;
 strip = &quot;symbols&quot;</code></pre>

You are probably looking at a debug build. On Linux, a release build (cargo build -r) is ~4.3M, and down to ~3.5M once stripped. This could be reduced further with some tricks applied to the release build profile.

Is It though? You won&#x27;t get it on an embedded device (maybe) but you could install a thousand of these tools and barely even notice the space being taken up on most machines

When you include the code for all the dependency features this uses, you probably do end up close to 100k LoC net, no?

Great catch! Comments mentioned getting it down to ~2MB but that’s still humongous.If you just think about how roughly (napkin math) 2MB can be 100k loc, that’s nuts

Glancing at the Cargo.toml, the package doesn&#x27;t define any features anyways. `cargo b --no-default-features` only applies to the packages you&#x27;re building, not their dependencies -- that would lead to very unpredictable behavior

Try `cargo build --release --no-default-features` to get a much smaller binary (~5-10MB) - Rust statically links dependencies but supports conditional compilation for optional features.

First off, the display looks great!Second off, I didn&#x27;t realize how deep the dep tree would be for this type of program -- 141 total! So much of it is the url crate, itself a dep of the git crate, but there&#x27;s a bunch of others too. I&#x27;m just getting into learning Rust -- is this typical of Rust projects or perhaps typical of TUI projects in general?(EDIT to strikeout) ~~The binary is also 53M as a result whereas &#x2F;usr&#x2F;sbin&#x2F;tree is 80K on my machine -- not really a problem on today&#x27;s storage, but very roughly 500-1000x different in size isn&#x27;t nothing.~~Maybe it&#x27;s linking-related? I don&#x27;t know how to check really.(EDIT: many have pointed out that you can run `cargo build --release` with other options to get a much smaller binary. Thanks for teaching me!)

No async which is nice. TIL that Rayon has an almost Occam like syntax:
<a href="https:&#x2F;&#x2F;github.com&#x2F;bgreenwell&#x2F;lstr&#x2F;blob&#x2F;44b9bbf118ca905581383d1ec35be88c2859e36e&#x2F;src&#x2F;main.rs#L110C21-L110C29">https:&#x2F;&#x2F;github.com&#x2F;bgreenwell&#x2F;lstr&#x2F;blob&#x2F;44b9bbf118ca90558138...</a>
although you subsequently went with a library that bundles parallel filesystem traversal.

Really appreciate all the comments and useful feedback (first Rust package). Especially ways to reduce the size of the binary!

That&#x27;s been similar to my experience. The ecosystem is extremely polished and smooth, the build tools and package manager and IDE support, all of it. Especially compared to C++ which I cuold barely get working here.

I appreciate the ecosystem of packages that seem really well maintained. I don’t love the syntax and find Rust harder to read and learn so far compared to something like golang (I’m used to R which is not a compiled language but has a great dev community).I do love the compiler and support tools built into Cargo (fmt, clippy, etc.).

So after writing this to learn Rust, what are your thoughts on Rust? What do you especially like and dislike about it, or what were you surprised about?

This looks awesome! Right up my alley.Side-note: what theme are you using in the linked gif? It&#x27;s right in the middle of my two favorite themes, onedark and gruvbox.

On interactive mode &quot;ls tree&quot; tools, an interesting one is broot.<a href="https:&#x2F;&#x2F;github.com&#x2F;Canop&#x2F;broot">https:&#x2F;&#x2F;github.com&#x2F;Canop&#x2F;broot</a>

I really love all the &quot;modern&quot; takes on classic tools by the Rust community.I&#x27;m using eza (aka exa), aliased as ls, which has &quot;tree&quot; built in (aliased as lt), amongst others, as replacement for &quot;ls&quot; and it&#x27;s one of my biggest production boosts in daily commandline use. Because eza has the tree built in, and the tree is also insanely fast, I won&#x27;t be needing this tool - yet. Maybe one day the interactive mode will pull me over.Congrats on releasing. And kudo&#x27;s to how well you&#x27;ve released it: solid README, good description, good-looking gifs with exactly the right feature highlights

Neat, looks like a combination of erdtree[0] and broot[1]. I use both on a daily basis, are there any features that stand out from the two?[0]: <a href="https:&#x2F;&#x2F;github.com&#x2F;solidiquis&#x2F;erdtree">https:&#x2F;&#x2F;github.com&#x2F;solidiquis&#x2F;erdtree</a>
[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;Canop&#x2F;broot">https:&#x2F;&#x2F;github.com&#x2F;Canop&#x2F;broot</a>

Hi HN,(First time poster!)I&#x27;m the author of `lstr`. I&#x27;ve always loved the classic Linux `tree` command for its simplicity, but I often found myself wanting more modern features like interactivity and Git integration. So, I decided to build my own version in Rust with a philosophy of being fast, minimalist, and interactive. It was also an excuse to help learn more about Rust\!Here&#x27;s a quick look at the interactive mode:<a href="https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;bgreenwell&#x2F;lstr&#x2F;main&#x2F;assets&#x2F;lstr-demo.gif" rel="nofollow">https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;bgreenwell&#x2F;lstr&#x2F;main&#x2F;asset...</a>I&#x27;ve just released v0.2.0 with some features I think this community might find useful:<pre><code> * **Interactive TUI Mode:** You can launch it with `lstr interactive`. It allows for keyboard-driven navigation, expanding&#x2F;collapsing directories, and opening files in your default editor.
 * **Git Status Integration:** Using the `-G` flag, `lstr` will show the Git status of every file and directory right in the tree output.
 * **Shell Integration:** This is my favorite feature. In interactive mode, you can press `Ctrl+s` to quit and have `lstr` print the selected path to stdout. This lets you pipe it into other commands or use it as a visual `cd`. For example, you can add this function to your `.bashrc`&#x2F;`.zshrc`:
 ```bash
 lcd() {
 local selected_path
 selected_path=&quot;$(lstr interactive -gG)&quot;
 if [[ -n &quot;$selected_path&quot; &amp;&amp; -d &quot;$selected_path&quot; ]]; then
 cd &quot;$selected_path&quot;
 fi
 }
 ```
 Then just run `lcd` to visually pick a directory and jump to it.
</code></pre>
It also supports file-type icons (via Nerd Fonts), file sizes, permissions, and respects your `.gitignore`.The project is open-source and I would love to get your feedback.GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;bgreenwell&#x2F;lstr">https:&#x2F;&#x2F;github.com&#x2F;bgreenwell&#x2F;lstr</a>Crates.io: <a href="https:&#x2F;&#x2F;crates.io&#x2F;crates&#x2F;lstr" rel="nofollow">https:&#x2F;&#x2F;crates.io&#x2F;crates&#x2F;lstr</a>Thanks for checking it out!

Show HN: Lstr – A modern, interactive tree command written in Rust