Might have needed the \s here

To be fair this is a terminal file manager… only a certain kind of person will be interested in the first place, and those people are likely to be more inclined to leave a star on GitHub.

Personally I believe the stars were achieved naturally but of course there’s no way to know and it never hurts to be skeptical.

As someone else said I think the shadowing works well here.

I do also wanna mention that depending on why you need this conversion, you could use impl AsRef<std::path::Path> for your function signature so it can accept &PathBuf or &Path. Then, just use that argument with e.g. p.as_ref() to get a &Path in the function body

Other people have given great reasons, but I will also mention that as someone who lives inside the terminal it’s often faster and easier to open it right there rather than getting a GUI one going. I do still use one for things that are easier to do with a graphical file manager though, no problem having both

That’s because it works very well, and the main developer is super active (I’ve contributed and made some plugins so have interacted with them a fair bit)

I mainly use it inside neovim actually, in place of the built in file manager or a file tree. Also use it if I want to quickly see the image files in a directory (it shows the images in the terminal), or rename a bunch of files. And then rarely for other file related activities as it makes exploring a directory very smooth

Fair play with taking the time to learn nix, currently tinkering with it and this stuff is no joke. Wish it wasn’t a DSL

Thanks hope you like it.

It parses files from different launchers like Steam or Bottles preaent on your system, and when the game is selected, it will spawn the command for launching the game directly via e.g. a steam command to launch that specific game ID. It doesn’t interact with desktop shortcuts in any way if that’s what you mean, though that is how it started

Thanks!

To be completely honest, I probably won’t use it again, at least for a while. While it’s nice to work with most of the time, I ran into a lot of weird niche issues that I had to either work around or come up with some hack to achieve the same effect, which was unfortunate. As a random example, trying to scroll to the top of the document every time a state was changed would not trigger the scroll consistently, making it pretty useless.

For a site like this, it would probably have been easier to just use a JS framework, or finally go and learn htmx