keybase.exe is not in path after windows install
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Not sure whether you'd consider this a bug. But after installing keybase_setup_386.exe on windows 10 the executable keybase.exe is not in my path. It ended up in .\AppData\Roaming\keybase\keybase.exe, which is a bit awkward to use.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the installation with keybase_setup_386.exe on Windows 10 and inspect where keybase.exe is placed under .\AppData\Roaming\keybase. Trace the installer entry point and verify how PATH is handled. Done means a fresh installation makes keybase.exe available through PATH, with the behavior verified after installation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100