[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread elextr via Github-comments
WFM. > if the software draws the string colors AFTER scalar and identifier_1 color, > these colors are ovewritten by string color, and that seems to be the deep > problem. No it doesn't work like that. What version of Geany are you using? -- Reply to this email directly or view it on

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
if the software prints the **string colors** AFTER **scalar and identifier_1** color, these colors are ovewritten by string color, and that seems to be the deep problem. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3860#issuecomment-2081494130

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
Have done that, opened via Tools, replaced all the file content with the configs you suggested and still not working. I closed geany, reopened, and even think that **bash** is taken by geany as **sh** too ? -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Colomban Wendling via Github-comments
> The bad news is that it doesn't work too. > I have added it, closed geany, reopen and all is the same. WFM, looks like that: Default: ![default](https://github.com/geany/geany/assets/793526/73d4a2cd-639d-46bf-8ff9-dd28c7e37a32) Adding `lexer.bash.styling.inside.string=1`

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
One question: what is the correct: altering via Geany Tools, ... or editing directly in the file /usr/share/geany/file... Because opening in Tools, **all lines appear commented** and is is different from the same file in /usr/share/geany/file... What is actually used ? -- Reply to this email

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
The bad news is that it doesn't work too. I have added it, closed geany, reopen and all is the same. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3860#issuecomment-2081480908 You are receiving this because you are subscribed to this thread. Message

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Colomban Wendling via Github-comments
Try adding this in *filetypes.sh* (you can open it from *Tools → Configuration files → Filetypes configuration files → Scripting languages*): ```ini [lexer_properties] lexer.bash.styling.inside.string=1 lexer.bash.styling.inside.backticks=1 lexer.bash.styling.inside.parameter=1

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
PHP uses "preprocessor" color for the dollar variables, not identifier_1 ( that sh/bash uses ) **The question is:** Why geany can draw php dollar variables interpolated in string correctly, but not for shellscript ? -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
An important observation: For single quoted string 'Single quoted string kills $dollar $vars' it is OK as they kill dollar variables. In this case, the string color is used. But double quotes "Double quotation keeps the $dollar $variables" they should be colored as identifier_1 as geany does

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
I thank the lexer.bash.styling.inside.string information. How to set it ? If Geany color application followed a simple rule, it would NOT depend on language neither of this config. The algorithm now paits string after the identifier_1 color with is for dollar variables. If just the identifier_1

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Sergio Abreu A. via Github-comments
I use vim and it always color the identifier with a different color. It does not matter if is shell script or php. If geany draws identifier_1 nicely out of the string and do not when the dollar variable is interpolated in a string it is geany weakness and I could myself show how to fix it Em

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread elextr via Github-comments
Bash and PHP are mentioned. AFAICT bash needs property `lexer.bash.styling.inside.string` set but the default is unset. Php styles `$word` inside strings as `SCE_HPHP_HSTRING_VARIABLE` so it depends on what it maps to and what the theme set it to. -- Reply to this email directly or view it

[Github-comments] Re: [geany/geany] color priority/precedence (Issue #3860)

2024-04-28 Thread Colomban Wendling via Github-comments
That's not how things work here, the identifier id either recognized as such anf given a separate style (which we might or might not draw the same as a string), or it's not recognized and thus is considered a string. Which language do you have issue with? -- Reply to this email directly or