tools: Fix compile-keymap default KcCGST values #653
Conversation
This file contains 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
Values may be read from the environment.
bluetech
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Values may be read from the environment!
While working on a xkbcomp MR I was very confused by
<BKSP>being mapped differently with and without an option that does not affect it. It turns out it is justcompile-keymapthat replaces null options with my env variable$XKB_DEFAULT_OPTIONS = terminate:ctrl_alt_bksp, as expected.But debugging with
--kccgstdid not help, because it does not take the environment into account.Now I am wondering how we could document this better in the tool and if how to read the env to output
usagewith correct default values.