Provide more helpful error message from shell access without FUSE
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Without the macOS Finder integration (FUSE) installed, when from a shell e..g cd /keybase/ is run, the command fails with a 'Permission denied' error. To solve this, the Finder integration must be enabled, but this is not obvious to the user.
This is a UX issue. It would help if:
- the Keybase 'macOS Finder integration' setting shows that it applies to the file system in general (e.g. for shell access), not just the Finder.
- the shell access (e.g.
cd /keybase/orls /keybase/) would respond with an error message telling the user about this Keybase setting, instead of 'Permission denied'.
Originally posted by @erikhuizinga in https://github.com/keybase/client/issues/23645#issuecomment-612072179
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
Start with the macOS Finder integration setting and the shell entry points represented by cd /keybase/ and ls /keybase/; the issue names no source files or tests. Trace how missing FUSE produces the current “Permission denied” response and how the setting is presented. Done means the setting clearly covers shell access and the command reports that it must be enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- cli, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100