[BUG] matching-negate-char is broken

[jaki]

Rofi version (rofi -v)

1.7.6

Configuration

https://gist.github.com/jaki/1e91c8f49be56d4ee288f71489baf459/raw/e99b21117cad712c6a537ec5174be3b40e537586/config.rasi

Theme

default

Timing report

n/a

Launch command

rofi -show run

Step to reproduce

Prepare config:

mv ~/.config/rofi ~/.config/rofi.$RANDOM
mkdir ~/.config/rofi
cat >~/.config/rofi/config.rasi <<EOT
configuration {
	matching-negate-char: '-';
}
EOT

git checkout c6f3cfb7d7c711f0a59fb364af4f74d9996c57e2~
make
./rofi -show run

...nothing wrong

git checkout c6f3cfb7d7c711f0a59fb364af4f74d9996c57e2
make
./rofi -show run

...throws error

/.../.config/rofi/config.rasi:1:16: Option: matching-negate-char needs to be set with a character not a String.

Expected behavior

nothing wrong

Actual behavior

aforementioned error

Additional information

Commit c6f3cfb breaks what PR #1131 fixed. Documentation still indicates

Character

Character value is always surrounded by single quotes (') and should contain a single character. It supports escaping.

matching-negate-char: '-';

but commit c6f3cfb goes against that. I tried reverting c6f3cfb but it causes some merge conflicts that I don't want to deal with.

Using wayland display server protocol

• No, I don't use the wayland display server protocol

I've checked if the issue exists in the latest stable release

• Yes, I have checked the problem exists in the latest stable version

[DaveDavenport]

yeah, that change should not have been committed.

[DaveDavenport]

Worked around it in GIT. Removed the 'Character' type from the CSS parser and internally use the string type for the character, that should fix this. If you can please test.

[jaki]

Yes, de4e10a fixes it.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.