Instead of hard coding a space after `make` for the default command, always put a space.
If the user changes the command, it's easy for them to remove the trailing space, and the argument can then change which command is run.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3825
-- Commit Summary --
* [Make Custom Target] Always put a space between command and argument
-- File Changes --
M src/build.c (8)
-- Patch Links --
https://github.com/geany/geany/pull/3825.patchhttps://github.com/geany/geany/pull/3825.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3825
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3825(a)github.com>
If I try to add a keyword in filetypes.langage.conf who start by the symbol, @, he will not be colored.
For example, the Zig language use builtins function who start by @, but I can't color them.
I used C coloration as base for custom Zig coloration, but with Rust lexer and tag parser, maybe a ctag problem ? I don't know.
I join my configuration file if you want to try.
[filetypes.ZigBasicSupport.zip](https://github.com/geany/geany/files/1494835…
And also, is it possible to define a coloration for every u or i followed by a number ? Zig can use them to specify any size of integer.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3830
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3830(a)github.com>
The `white_space` color theme setting can change the fore- and background colors of the dots to show spaces as well as the arrows drawn for tabs, if enabled.
However, the setting is tied to both of them and my perception of the two is very distinct. In my usual setup I use 1440p 24" displays and the dots for whitespaces are actually a single pixel which is almost invisible for me with the default scheme while the tab arrows are quite clearly visible. I have played around with the `white_space` settings to improve the situation and ended up using a slightly grey background (`white_space=0x808080;0xf7f7f7;true;true`) which I am currently testing. However, I am not totally happy with that and it is just a workaround. What I would really wish for would be more pixels in the space dot to make it most distinct relative to the arrow.
Maybe my setup is a corner-case combination of font size, monitor attributes and eyes but it would be nice if the dot shape could be changed in some way, which I think there isn't yet(?).
I have attached a photo of the situation with the default color scheme. It doesn't do justice to my perception where it is much worse but even here you can make out the arrow way better than the dots and I think it is easy to imagine that the dots get much harder to recognize when overall conditions deteriorate (e.g., the lens/eye is moved farther away from the screen).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3829
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3829(a)github.com>
Always reset backgrounds first on any dialog response, then set again if necessary. When showing a dialog this was only done when using the document selected text, but the document could have changed e.g. to contain the previously unmatched search text, yet the background remained. Also the Find All responses didn't clear the background even when successful. This fixes those situations.
Set search entry background when there's a regex or escape error.
Set replace text entry background when there's an escape error.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3828
-- Commit Summary --
* Make Find set entry background on error
* Make Replace set entry backgrounds on error
* Always reset entry backgrounds on dialog response
-- File Changes --
M src/search.c (53)
M src/ui_utils.c (5)
-- Patch Links --
https://github.com/geany/geany/pull/3828.patchhttps://github.com/geany/geany/pull/3828.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3828
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3828(a)github.com>
See title
geany 2.1 (git >= 06b8e6b1c) (built on 2024-04-05 with GTK 3.24.33, GLib 2.72.4)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3824
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3824(a)github.com>
`dialogs_show_input_full` had grown into a monster taking 2 different sets of callbacks.
The complexity can be removed if:
* the caller creates the combo/entry widget, as they can then connect any special signals to it themselves.
* the caller runs the dialog even when modal
I was also tempted to remove the callback for `dialogs_show_input_persistent`, but I haven't done that here.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3826
-- Commit Summary --
* [Input Dialog refactor] Replace 5 parameters with 1
* Add entry parameter for flexibility
* Also wrap label for dialogs_show_input_numeric
-- File Changes --
M src/dialogs.c (113)
-- Patch Links --
https://github.com/geany/geany/pull/3826.patchhttps://github.com/geany/geany/pull/3826.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3826
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3826(a)github.com>