zellij --version: 0.37.2
uname -av or ver(Windows): Linux MSI 5.15.90.1-microsoft-standard-WSL2
Further information
I updated zellij from version 0.36.0 to 0.37.2 and did not change any configuration files. Upon running zellij it immediately quit and print De serialization error: Expected a valid node entry. to the terminal. Nothing was added to the log file.
After reinstalling zellij version 0.36.0 it ran successfully, while still logging the following:
There was a syntax error in a theme definition file. This theme file was in the theme directory and did not have a theme that was currently being used.
The difference of handling the error between the 2 version is what I consider the bug:
Version 0.37.2 quits the program without logging the error and prints De serialization error: Expected a valid node entry.
Version 0.36.2 will run the program and log the same error
I would believe the intended behavior in Version 0.37.2 would be the same behavior as Version 0.36.2 .
This was not an easy error to diagnose as there was little information given. I had no change in configuration and not much of a direction to head towards in order to solve it. Zellij so nicely handles config.kdl syntax errors, and such an implementation for handling theme configuration files would be helpful for users.
Basic information
zellij --version
: 0.37.2uname -av
orver
(Windows): Linux MSI 5.15.90.1-microsoft-standard-WSL2Further information I updated
zellij
from version 0.36.0 to 0.37.2 and did not change any configuration files. Upon runningzellij
it immediately quit and printDe serialization error: Expected a valid node entry.
to the terminal. Nothing was added to the log file.After reinstalling zellij version 0.36.0 it ran successfully, while still logging the following:
There was a syntax error in a theme definition file. This theme file was in the theme directory and did not have a theme that was currently being used.
The difference of handling the error between the 2 version is what I consider the bug:
De serialization error: Expected a valid node entry.
I would believe the intended behavior in Version 0.37.2 would be the same behavior as Version 0.36.2 .
This was not an easy error to diagnose as there was little information given. I had no change in configuration and not much of a direction to head towards in order to solve it. Zellij so nicely handles config.kdl syntax errors, and such an implementation for handling theme configuration files would be helpful for users.
Incorrectly formatted file for reference