Hello,

fzf is installed via the openbsd package manager like this :

> % pkg_info -L fzf
Information for inst:fzf-0.21.1

Files:
/usr/local/bin/fzf
/usr/local/bin/fzf-tmux
/usr/local/man/man1/fzf-tmux.1
/usr/local/man/man1/fzf.1
/usr/local/share/doc/pkg-readmes/fzf
/usr/local/share/fish/functions/fzf-key-bindings.fish
/usr/local/share/fzf/bash/completion.bash
/usr/local/share/fz

any plans for a Linux ARM build? if nobody else is on it or has attempted it, i can give it a try.

An alias for --decorations always so I can pipe the decorations when doing something like bat FILE | gview -. …but without the ^M's.

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

Topic

So sometimes when I am pushing to a branch and it has diverged from the remote, a little pop up shows up saying would you like to force push. Instinctively I press enter instead of escape which ends up force pushing

Your thoughts

I was hoping there would be an option to disable this specific behavior or just disable force pushing all throughout lazygit.

I feel like this m

I see a lot of fd users that seem to think that they need to add "{}" to all commands. Some users also seem to think that the closing semicolon (which needs to be escaped) \; is required:

fd … -x command "{}" \;

In reality, 90% of the --exec use cases can be written without the "{}" part (which fd adds, if it is ommitted) because the file entry often comes last. The semic

Current behavior

Expected behavior

Relevant Zsh configuration (.zshrc)

Irrelevant with the issue

Environment

Spaceship version: `3.11

Solaris and Illumos use Bash as the default shell. However, currently bash-it does not work as expected on them.

This can be fixed as described, tested, and confirmed here.

Here's what I suggest:

• In install.sh, check for `$0S