> 1. […] call_tips are entirely unaffected by whatever I put in the call_tips > line.
WFM, with `call_tips=#c00;yellow;true;true` I get this: <img width="567" height="77" alt="themed-calltips" src="https://github.com/user-attachments/assets/ab782a29-66e4-4fee-b19d-abedd1ce8cc9"; /> Which is admittedly ugly, but definitely not my DE's theme :) > 2\. I'm still not too sure how to reproduce whatever effect string_eol is > supposed to have. I'll keep looking for languages like that and see what I > can manage. ```c strstr("hello ``` The string `"hello` is not terminated properly, as C doesn't allow a bare `\n` inside a string, and is thus styled as `string_eol`. > 3\. I was not seeing anything because I was using a construct > like:`label=keyword;;true` which shows up (in a Makefile, for example) in the > default color (NOT the keyword color), though it is bold. OTOH, using > `label=keyword,bold,italic` does result in labels that are in the "keyword" > color as well as being bold and italic. This surprised me since > `comment=dark_green;;;true` does make comments dark green and italic, but > `comment=dark_green,italic` basically turns off comments, leaving them in the > default color with no italics. This is due to you mixing the syntax for the different things. Admittedly it's not very intuitive but: * `color;;;true` (with semicolons) means "set foreground color to `color` and make the text italic". The syntax with semicolons accept colors either as names or `#hex`, *not style names*. * `style_name,bold,italic` (with commas) means "set everything the same as style_name, but make it also bold and italic". The syntax with commas accepts another style name *not colors*. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/4381#discussioncomment-13854927 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/repo-discussions/4381/comments/[email protected]>
