Open alexhitchins opened 8 years ago
I assume it should be added to the PATH environment variable?
As far as I know this does not happen by default. (intended?) A workaround if you don't know how or don't want to add Keybase to %PATH%
is to simply launch Keybase Shell
which automatically runs where the binaries are runnable.
can you run
sudo updatedb
sudo locate keybase | less
You should be able to see if the binary exists anywhere if it does make sure your PATH is correct. On debian through APT it installed right on /usr/bin/keybase
I'm running on Windows. I will go back to this issue and see if it's still occurring. Perhaps an option in the installer to ask if you want the install dir added to PATH on Windows?
According to @zanderz it's entirely intentional and not a bug.
Steps I followed;
1) Install keybase app 2) Go to command line 3) Type keybase (just to determine if app installed) 4) Receive "'keybase' is not recognised as an internal or external command, operable program or batch file."
I assume it should be added to the PATH environment variable? I can't see any entry related to KeyBase.
Windows 10 64x - Version 1511, latest Keybase Build.