Question: Unset option. #71
Comments
|
Mhm, I've only looked at the code right now but I think this may be a bug. I would expect that such an entry matches with an empty value. At least that's what I'd expect Xlib to do. I'll have a look at it and push a fix if necessary. Can't believe this wasn't in the tests yet. |
Airblader
added a commit
that referenced
this issue
Nov 24, 2016
This patch fixes how an entry like
some.component:
is parsed. Previously, this would error out and ignore the entry,
but the correct behavior is to parse it and assign the empty value
to it. This is needed for applications to differentiate between a
resource not being defined and it having an empty value.
fixes #71
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way to see if an option is unset?
If I do:
It does not find a match when looking it up using:
xcb_xrm_resource_get_string.(kind of expected)But is there anyway to see that is specified but not set.
The text was updated successfully, but these errors were encountered: