Errors parcing Kitty's config
Describe the bug
An error occurring during kitty launch (after copying config using linutil)
To Reproduce
Steps to reproduce the behavior:
- Fresh Archlinux setup (manually, not using linutil) I installed kitty and copied kitty's config file (thought it was cause of my first Arch setup)
- Fresh install of Debian bookworm - everything OK. But then upgraded to Debian SID - the error repeated here
- Both installations on Gnome Boxes
Expected behavior
simple and clean launch of kitty terminal
Screenshots
Additional context
Apologies if there is smthing wrong. This is my very first bug report.
Checklist
- [x] I checked for duplicate issues.
- [x] I checked already existing discussions.
- [x] This issue is not included in the roadmap.
- [x] This issue is present on stable branch (did not test using dev branch).
GNOME BOXES HELL YEAH
Looks like the nord.conf file is included twice: at the very beginning and the very end of the kitty.conf. I know absolutely nothing about Kitty, but it doesn't seem to like that.
https://github.com/ChrisTitusTech/dwm-titus/blob/main/config/kitty/kitty.conf
If there's any settings in the nord.conf file that are also present in the kitty.conf file, then it would be an important consideration if the nord.conf should be included at the very beginning or at the very end, since those settings would most likely override each other. I assume latest occurrence "wins" (as in, will be the active setting).
Somebody who actually uses and knows something about Kitty might go to the dwm-titus repo and create a PR.
Looks like the
nord.conffile is included twice: at the very beginning and the very end of thekitty.conf. I know absolutely nothing about Kitty, but it doesn't seem to like that.https://github.com/ChrisTitusTech/dwm-titus/blob/main/config/kitty/kitty.conf
If there's any settings in the
nord.conffile that are also present in thekitty.conffile, then it would be an important consideration if thenord.confshould be included at the very beginning or at the very end, since those settings would most likely override each other. I assume latest occurrence "wins" (as in, will be the active setting).Somebody who actually uses and knows something about Kitty might go to the
dwm-titusrepo and create a PR.
Well, thnx. Need to dig deeper into that. Because, in Debian it happend only when I switched to sid. On stanfard 12.9 everything's fine. Need to test it on a prod. machine and try to update it the same way, see if the issue remains.
/close fixed with https://github.com/ChrisTitusTech/dwm-titus/commit/6731d647fd75e115639d1a626608d549725211c6