xplr.vim
fzf
xplr.vim | fzf | |
---|---|---|
10 | 407 | |
19 | 59,920 | |
- | - | |
0.0 | 9.6 | |
over 1 year ago | 4 days ago | |
Vim Script | Go | |
BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
xplr.vim
-
What file explorer do you use?
xplr.vim
-
What are your favorite Rust-powered Linux programs?
Xplr, a hackable, minimal, fast TUI file explorer
- Does a based GTK file manager even exist out there?
-
Some useful linux terminal application or plugging ?
xplr (TUI file explorer)
-
fm-nvim: Neovim plugin that lets you use your favorite terminal file managers from within Neovim
The supported file managers (as of right now) are nnn, lf, ranger, xplr, and vifm.
-
xplr features updated
Being super configurable, [xplr][xplr] by design integrates well with other tools. Try this fzf integration tutorial or this vim plugin if you are not convinced yet.
-
[help] Looking for Lua veterans to help with embedded Lua api
Fun fact: xplr has a vim plugin.
-
Do you use a file tree explorer?
I use xplr with plugin for exploring and fzf for searching.
-
xplr - A hackable, minimal, fast TUI file explorer
View on GitHub
-
Looking for a new plugin owner
Now, I would like to clean up, probably improve and turn xplr.vim into a real and well maintained plugin, with its own dedicated variables and docs. However, I have no experience with vim plugin development and decided that it's better to offload this task to someone who knows their way around the (neo)vim plugin system, so that I can focus more on xplr's development instead.
fzf
-
Ask HN: Any tool for managing large and variable command lines?
In addition, I think bash's `operate-and-get-next` can be very helpful. When you go back through your shell history, you can hit Ctrl+o instead of enter and it will execute the command then put the next one in your history on the command line, and keep track of where you are in your history. This way, you can rerun a bunch of commands by going to the first one and Ctrl+o till you are done. And you can edit those commands and hit Ctrl+o and still go to the next previously run command.
Note: fzf's history search feature breaks this. https://github.com/junegunn/fzf/issues/2399
-
pyfzf : Python Fuzzy Finder
fzf : https://github.com/junegunn/fzf
- Command Line Fuzzy Search
-
So You Think You Know Git – Git Tips and Tricks by Scott Chacon
Those are the most used aliases in my gitconfig.
"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf
"git gone" removes local branches that don't exist on the remote.
"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide
-
Which command did you run 1731 days ago?
> my history is so noisy I had to find another way
The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].
[1]: https://github.com/junegunn/fzf#search-syntax
[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...
-
Z – Jump Around
You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.
I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.
¹ https://github.com/sharkdp/fd
² https://github.com/junegunn/fzf
-
alacritty-themes not working any more!!!
View on GitHub
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues
[1] https://github.com/junegunn/fzf
[2] https://github.com/PatrickF1/fzf.fish
-
Ugrep – a more powerful, ultra fast, user-friendly, compatible grep
You can also use fzf with ripgrep to great effect:
[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...
- Tell HN: My Favorite Tools
What are some alternatives?
nnn.vim - File manager for vim/neovim powered by n³
peco - Simplistic interactive filtering tool
xclip - Command line interface to the X11 clipboard
zsh-autocomplete - 🤖 Real-time type-ahead completion for Zsh. Asynchronous find-as-you-type autocompletion.
xplr - A hackable, minimal, fast TUI file explorer
z - z - jump around
noice - Branch of the noice file browser from http://git.2f30.org/noice
zsh-autosuggestions - Fish-like autosuggestions for zsh
fm-nvim - 🗂 Neovim plugin that lets you use your favorite terminal file managers (and fuzzy finders) from within Neovim.
mcfly - Fly through your shell history. Great Scott!
ranger - A VIM-inspired filemanager for the console