fix(install): seed both Roman and Hiragana Google IME modes; housekeeping - #303
Merged
Merged
Conversation
Enable both 英数 and ひらがな input modes so the 英数 key toggle persists across app switches (HIToolbox only remembers enabled modes, keyed by com.apple.inputmethod.Japanese*, not com.google.* IDs). Also: add claude desktop cask; bump nvim-lspconfig / nvim-treesitter pins. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
com.apple.inputmethod.Japanese*input-mode keysclaudedesktop app casknvim-lspconfigandnvim-treesitterpinsWhy
The 英数 key only toggles a mode that macOS remembers if that mode is an enabled input source; otherwise every app switch reinitializes the input context back to Hiragana. HIToolbox stores "Input Mode" using the
com.apple.inputmethod.Japanese*keys from the IME's tsInputModeListKey, not thecom.google.*TISInputSourceIDs, so the previous seeding never matched an enabled mode.Test plan
brew bundle checksucceeds with the new cask entry🤖 Generated with Claude Code