-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: strings can't start with "?" #15
Conversation
This starts to cause issues with config keys such as |
Can you please add some test cases? |
^^^ is there a problem in the way this is parsed? According to the docs, only |
hmm, that's odd. It seems like the ? is ignored for everything that accepts path input. Ghostty doesn't seem to be sending warnings when the |
Could also be a bug, I'm running an unstable git version currently |
Until it's officially documented that those properties treat a leading Introducing it in the future doesn't seem like it would be a breaking change as it wouldn't introduce another level to the tree in a way that existing queries might break. |
@gerblesh We can generalize it into a |
seems like it's also an issue upstream: ghostty-org/ghostty#4509 |
0386a1e
to
2a7bec8
Compare
fix: path directives
b824279
to
cbd14f1
Compare
Added some extra tests and squashed the commits, should be able to merge now |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
This should fix the highlighting of "?" for optional filepaths in the
config-file
directive