Suggestion: `yabai doctor` to debug issues
- Dominant language
- C
- Stars
- 29.6k
- Forks
- 750
- PR merge metrics
- No merged PRs in 30d
Description
I wrote a script to help me debug issues with yabai and skhd. I'm LOVING it. I used to spend time every month or so debugging why it had stopped working and now it's so easy!!! The one I trigger the most often is the secure keyboard setting. This is a game-changer, and I wanted to share!
```
FAIL secure keyboard entry is on (pid 665, /Applications/Slack.app/Contents/MacOS/Slack); skhd gets no keys. Turn it off in that app's menu
```
https://github.com/IanEdington/dotfiles/blob/main/macOS/yabai/doctor.sh
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the linked doctor.sh script first, focusing on its secure keyboard entry check and the diagnostic message it produces for skhd. Then inspect yabai's command entry points to determine how a `yabai doctor` command could expose this behavior. Done means the proposed diagnostic is available through yabai rather than only the external script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos, shell
- Domain
- cli, operating-systems, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100