Clarify the common use case for --config-file-name
This commit is contained in:
parent
ddf36383b4
commit
e16e3c1582
@ -553,7 +553,9 @@ instead of changing kitty.conf.
|
|||||||
default=kitty.conf
|
default=kitty.conf
|
||||||
The name or path to the config file to edit. Relative paths are interpreted
|
The name or path to the config file to edit. Relative paths are interpreted
|
||||||
with respect to the kitty config directory. By default the kitty config file,
|
with respect to the kitty config directory. By default the kitty config file,
|
||||||
kitty.conf is edited.
|
kitty.conf is edited. This is most useful if you add :code:`include current-theme.conf`
|
||||||
|
to your kitty.conf and then have the kitten operate only on :file:`current-theme.conf`,
|
||||||
|
allowing :code:`kitty.conf` to remain unchanged.
|
||||||
'''.format
|
'''.format
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user