You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--config-file-name <CONFIG_FILE_NAME>
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, kitty.conf is edited. This is most useful if you add include themes.conf to your kitty.conf and then have the kitten operate only on themes.conf, allowing kitty.conf to remain unchanged. Default: kitty.conf
which implies that the --config-file-name option accepts both relative paths and absolute paths. But when I pass an absolute path, it is erroneously interpreted as a relative path.
Error: open /home/<your_user_name>/.config/kitty/home/<your_user_name>/.config/kitty/dark_or_light.conf.atomic-write-144744982: no such file or directory
Environment details
kitty 0.29.2 created by Kovid Goyal
Linux <machine_name> 6.1.51-1-MANJARO #1 SMP PREEMPT_DYNAMIC Sat Sep 2 23:22:36 UTC 2023 x86_64
Manjaro Linux 6.1.51-1-MANJARO (<machine_name>) (/dev/tty)
[...]
I'm pretty sure this used to work, and it stopped working a few months ago. (Sorry, not sure when exactly it stopped working.)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
According to the doc,
which implies that the
--config-file-name
option accepts both relative paths and absolute paths. But when I pass an absolute path, it is erroneously interpreted as a relative path.To Reproduce
Steps to reproduce the behavior:
kitty +kitten themes --reload-in=all --config-file-name /home/<your_user_name>/.config/kitty/dark_or_light.conf "Modus Operandi"
Error: open /home/<your_user_name>/.config/kitty/home/<your_user_name>/.config/kitty/dark_or_light.conf.atomic-write-144744982: no such file or directory
Environment details
I'm pretty sure this used to work, and it stopped working a few months ago. (Sorry, not sure when exactly it stopped working.)
The text was updated successfully, but these errors were encountered: