fix README tag issue
This commit is contained in:
parent
4ab6c4f100
commit
c0d94b2de7
@ -10,7 +10,7 @@ Below is a simple example demonstrating two system-wide theme switches:
|
|||||||
|
|
||||||
This GIF shows two `symconf` calls, the first of which applies a `gruvbox` dark theme and
|
This GIF shows two `symconf` calls, the first of which applies a `gruvbox` dark theme and
|
||||||
the second a dark [`monobiome`][1] variant. Each call (of the form `symconf config -m dark -s
|
the second a dark [`monobiome`][1] variant. Each call (of the form `symconf config -m dark -s
|
||||||
<style>`) indicates a dark mode preference and a particular color palette that should be
|
style`) indicates a dark mode preference and a particular color palette that should be
|
||||||
used when populating config file templates. Specifically, in this example, invoking
|
used when populating config file templates. Specifically, in this example, invoking
|
||||||
`symconf` results in the following app-specific config updates:
|
`symconf` results in the following app-specific config updates:
|
||||||
|
|
||||||
|
@ -544,7 +544,7 @@ class ConfigManager:
|
|||||||
2. Get matching user config files via ``get_matching_configs()``
|
2. Get matching user config files via ``get_matching_configs()``
|
||||||
3. Get matching template config files and the aggregate template dict via
|
3. Get matching template config files and the aggregate template dict via
|
||||||
``get_matching_templates()``
|
``get_matching_templates()``
|
||||||
4. Interleave the two the result sets by pathname and match quality. Template
|
4. Interleave the two result sets by pathname and match quality. Template
|
||||||
matches are preferred in the case of tied scores. This resolves any
|
matches are preferred in the case of tied scores. This resolves any
|
||||||
pathname clashes across matching files.
|
pathname clashes across matching files.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user