You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the Installation Instructions suggests, when we use sudo apt-get install fzf to install fzf, we get fzf v0.21.0-1. This version was released on 13rd March 2020. There have been 289 commits to master since that release. So, the users who installed fzf using sudo apt install fzf or sudo apt-get install fzf are using an outdated version of fzf. This could be solved by creating a PPA to contain the latest version of fzf and changing the installation instructions to add that PPA using apt-add-repository and then installing fzf, to get the latest version of fzf.
This issue is not shell specific since everyone who installed using apt or apt-get would have this issue.
I selected I have the latest version because I cloned the repository and used the install script. This can be done too, but using a PPA is much more convenient to users.
The text was updated successfully, but these errors were encountered:
man fzf
)Info
Problem / Steps to reproduce
As the Installation Instructions suggests, when we use
sudo apt-get install fzf
to install fzf, we get fzf v0.21.0-1. This version was released on 13rd March 2020. There have been 289 commits to master since that release. So, the users who installed fzf usingsudo apt install fzf
orsudo apt-get install fzf
are using an outdated version of fzf. This could be solved by creating a PPA to contain the latest version of fzf and changing the installation instructions to add that PPA usingapt-add-repository
and then installing fzf, to get the latest version of fzf.This issue is not shell specific since everyone who installed using
apt
orapt-get
would have this issue.I selected I have the latest version because I cloned the repository and used the install script. This can be done too, but using a PPA is much more convenient to users.
The text was updated successfully, but these errors were encountered: