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
Hello, I'm trying to make theme like visual studio code have (default dark theme).
So, I founded some strange cases, or absence of some expected things.
bugs
third hyphen option affects following string argument with blue color (33), I can't found how to redefine this
more strange things with arguments
second argument have default white color
path after source command is blue (33), while I defined section [paths] with orange 173
builtin have higher priority than subcommand, does it expected? looks less readable for me
absence of expected things
it's not possible to make different colors for left / right parts of assign statement
not possible to have custom colors for some special keywords
Where token parsing rules are located? Probably I'll fix smth.
Also last not important question / feature request.
Does it possible to define my custom colors at ini?
it's not handy to use numbers, better define colors with some name
Describe the bug
Hello, I'm trying to make theme like visual studio code have (default dark theme).
So, I founded some strange cases, or absence of some expected things.
bugs
[paths]
with orange173
buffer
not recognized at this caseabsence of expected things
Where token parsing rules are located? Probably I'll fix smth.
Also last not important question / feature request.
Does it possible to define my custom colors at ini?
it's not handy to use numbers, better define colors with some name
dark-code.ini
Steps to reproduce
screenshots show reproducing
Expected behavior
screenshots show expected
Screenshots and recordings
No response
Operating System & Version
linux-gnu | ubuntu | x86_64 | x86_64 | x86_64 x86_64
Zsh version
zsh 5.8 (x86_64-ubuntu-linux-gnu)
Terminal emulator
screen-256color
If using WSL on Windows, which version of WSL
WSL 2
Additional context
No response
The text was updated successfully, but these errors were encountered: