Using broot as an fzf-like path completer and interactive folder jumper in Zsh

andydecleyre.github.io

cross-posted to:
zsh@programming.dev

Using broot as an fzf-like path completer and interactive folder jumper in Zsh

andydecleyre.github.io

Andy@programming.dev to

Shell Scripting@programming.devEnglish · 1 year ago

cross-posted to:
zsh@programming.dev

Broot is a great file manager TUI which can be adapted for very specific workflows. But it takes some configuration up front to get things going, even for the basics. I’ll go over some of my own configurations for using it from Zsh: Minimum Suggested Setup: wrap broot in a Zsh function launch it with a non-disruptive shortcut Broot Basics: basic broot configuration basic broot usage Seamless Zsh Hookups: drill down and fuzzy filter to set your working folder complete a file argument My dotfiles containing the snippets in this post are on GitHub at dotfiles-broot and dotfiles-zsh/broot.zsh.

Hello! I love broot. It’s not my own project, but this blog post is, so feel free to send any questions or insults my way.

Previews:

You must log in or register to comment.

Chat

Shell Scripting@programming.dev

shell@programming.dev

Create a post

You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !shell@programming.dev

From Ash, Bash and Csh to Xonsh, Ysh and Zsh; all shell languages are welcome here!

Rules:

Follow Lemmy rules!
Posts must relate to shell scripting. (See bottom of sidebar for more information.)
Only make helpful replies to questions. This is not the place for low effort joke answers.
No discussion about piracy or hacking.
If you find a solution to your problem by other means, please take your time to write down the steps you used to solve your problem in the original post. You can potentially help others having the same problem!
These rules will change as the community grows.

Keep posts about shell scripting! Here are some guidelines to help:

Allowed: Release Announcement of a command-line program designed for scripted use (e.g. bash, bats, awk, jq, coreutils/moreutils)
Allowed: Tutorials on using shell languages or supplementary tools designed for scripted use
Allowed: Code review/help requests for shell languages or supplementary tools designed for scripted use
NOT Allowed: Announcement of a CLI or TUI program that is not designed for scripted use (Yes, your fancy Zsh plugin which pretty-prints the date and time using only builtins is very cool, but unless you actually want to discuss the code itself, please check out !commandline instead!)
NOT Allowed: Domain-specific tutorials that do not involve shell scripting as a core component (e.g. docker-compose, ansible, nix). If you really love one of these, I’m sure there’s a community out there ready to talk about them!
NOT Allowed: Code review requests for non-shell programming languages and configuration languages (e.g. Python, Yaml)

In general, if your submission text is primarily shell code, then it is welcome here!

Visibility: Public

This community can be federated to other instances and be posted/commented in by their users.

1 user / day
1 user / week
44 users / month
44 users / 6 months
1 local subscriber
1.44K subscribers
37 Posts
11 Comments
Modlog