Repository navigation
packaging: ship the config schema under /usr/share/lmtt - #9
Merged
Merged
Conversation
lmtt-config refreshes ~/.config/lmtt/config-schema.json on every run, so a settings UI that renders the same schema (dials' Appearance page) had nothing to read on a box that never ran the TUI. Install the bundled asset as /usr/share/lmtt/config-schema.json on both distros; the user copy still wins when present.
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.
dials' Appearance page (MasonRhodesDev/dials, appearance-page branch) renders lmtt's config schema. lmtt-config only writes it to
~/.config/lmtt/config-schema.jsonon each run, so a fresh install had nothing to read. Install the bundledlmtt-config-tui/assets/config-schema.jsonas/usr/share/lmtt/config-schema.jsonin the PKGBUILD and the spec (the spec's%{_datadir}/lmtt/directory entry already covers it). The user copy still takes precedence.