Live data from Hacker News

Fzf – the basics part 1 – layout

qmacro.org

11–20 of 40 posts

Re: Fzf – the basics part 1 – layout

#11

Fzf might be my most used command line utility. That and autojump (alias to j).

I use z[0] in place of autojump. That way I don't need to install Python solely for autojump. This is especially true, when sshing to servers. [0]: https://github.com/rupa/z

or its zsh native port https://github.com/agkozak/zsh-z

Re: Fzf – the basics part 1 – layout

#12

Fzf might be my most used command line utility. That and autojump (alias to j).

I use z[0] in place of autojump. That way I don't need to install Python solely for autojump. This is especially true, when sshing to servers. [0]: https://github.com/rupa/z

Theres also fasd. It has z emulation.

https://github.com/clvv/fasd

Re: Fzf – the basics part 1 – layout

#13
post #6
post #2

fzy[1] is a less bloated alternative, written in C. fzf is neat, but it does too much. [1]: https://github.com/jhawthorn/fzy

There's also skim[1], which would be a Rust fzy alternative. But neither fzy nor skim quite do what fzf does, which is offer an simple feature-filled experience out of the box. The big draw is fzf Just Works™. I don't mind that it feels bloated and slow sometimes, because I don't want to spend a week figuring out how to make the other two do what fzf does without configuration or drama, and all the speed improvements…

I really wish skim ran on Windows :(

Re: Fzf – the basics part 1 – layout

#14
My favorite ~/.gitconfig [alias] that uses fzf:

  # Allows you to easily pick what to rebase
  frbi = "!f() { git rebase -i $(git log --pretty=oneline --color=always | fzf --ansi | cut -d ' ' -f1)^ ; }; f"
Then just do:

  git frbi

Re: Fzf – the basics part 1 – layout

#15
post #6

Earlier quoted context omitted.

There's also skim[1], which would be a Rust fzy alternative. But neither fzy nor skim quite do what fzf does, which is offer an simple feature-filled experience out of the box. The big draw is fzf Just Works™. I don't mind that it feels bloated and slow sometimes, because I don't want to spend a week figuring out how to make the other two do what fzf does without configuration or drama, and all the speed improvements…

I really wish skim ran on Windows :(

There's always WSL ¯\_(ツ)_/¯

Re: Fzf – the basics part 1 – layout

#18
post #2

fzy[1] is a less bloated alternative, written in C. fzf is neat, but it does too much. [1]: https://github.com/jhawthorn/fzy

The real advantage of fzy over fzf is that fzy is actually better at guessing what you want (the documentation claims it's also faster but I never noticed a difference).

That fzy also forces you to think about good input providers (like fd instead of find) is just following the Unix philosophy of one tool doing what it's best at.

Re: Fzf – the basics part 1 – layout

#19

Fzf might be my most used command line utility. That and autojump (alias to j).

I use z[0] in place of autojump. That way I don't need to install Python solely for autojump. This is especially true, when sshing to servers. [0]: https://github.com/rupa/z

I've moved to https://github.com/ajeetdsouza/zoxide/ from z, as it can also show you a list of matching directories using fzf
Post reply on HN