Fixes #1363.
Similar to #1750, this disables pref widgets that are overridden by an open project. (It doesn't disable the frame label). Instead of editing a translatable label, this adds an info image next to the frame/widget label. A tooltip is set to show when the mouse is over the label or the image. This doesn't try to change the tooltip for disabled widgets, I didn't find a way to implement that easily and cleanly.

This approach can also be used to indicate which prefs are overridden by document-specific settings.
ATM this only affects the 'Saving files' prefs, but I can add the others.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2316
-- Commit Summary --
* Prefs dialog: Disable overridden pref widgets when project is open
-- File Changes --
M data/geany.glade (32)
M src/prefs.c (9)
-- Patch Links --
https://github.com/geany/geany/pull/2316.patchhttps://github.com/geany/geany/pull/2316.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2316
Depends on #2301, that should be merged first. (Could be worked around if necessary).
Currently the user can manually edit `geany.conf` or the project `.conf` to add filetype-independent execute commands which silently override the filetype execute ones. It's not really explained in the manual (but Lex says it's in the Wiki page), my guess is it's not used much.
This creates a new group of build commands - independent execute commands. These appear in the build menu after the filetype execute commands.
This is more flexible for the user and allows for adding GUI configurability to the 'Set Build Commands' dialog (which I can do in another pull).
This adds a keybinding for the first filetype-independent execute command, which defaults to Shift+F5.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2307
-- Commit Summary --
* build.c: Replace return_cmd_if macros with simpler BREAK_IF_CMD macro
* Replace unhygienic macro calls with array of struct
* Begin separating filetype-independent execute commands from FT execute
* Replace run_info with run_pids
* load & save independent exec group instead of ft exec
* Make build_run_cmd support independent execute & add keybinding
* Show independent run menu items
-- File Changes --
M TODO (1)
M src/build.c (232)
M src/build.h (2)
M src/keybindings.c (2)
M src/keybindings.h (5)
-- Patch Links --
https://github.com/geany/geany/pull/2307.patchhttps://github.com/geany/geany/pull/2307.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2307
The GLib docs say: "Typically, format should end with its own new-line character":
https://developer.gnome.org/glib/stable/glib-Warnings-and-Assertions.html#g…
* Not including a newline is more flexible as the caller can conditionally print part of a line, then the remaining part and a newline.
* Almost all the uses of g_print and g_printerr in geany and geany-plugins already include a newline at the end of `msg`. Printing two newlines is annoying.
* This adds a newline for the remaining cases in geany.
* I have a pull ready for geany-plugins, will edit this line when submitted. Only needed to change one line.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2309
-- Commit Summary --
* g_print handler: Don't add newline
* g_printerr handler: Don't add newline
-- File Changes --
M src/log.c (8)
M src/pluginutils.c (2)
M src/tagmanager/tm_workspace.c (2)
M src/utils.c (4)
-- Patch Links --
https://github.com/geany/geany/pull/2309.patchhttps://github.com/geany/geany/pull/2309.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2309
* The build docs often refer to "filetype commands" or "independent commands" when they mean *build* commands. Clarify these. (This is useful anyway, but particularly if I/we finish #2307)
* Fix some uses of "Build Menu Commands dialog" when it should be "Set Build Commands dialog".
* Various tweaks to aid reading. Remove some unnecessary paragraph breaks.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2326
-- Commit Summary --
* docs: Clarify that "filetype & independent commands" mean build commands
* Tweak build docs
* Rename superseded "Build menu commands" command to "Set Build Commands"
-- File Changes --
M doc/geany.txt (117)
-- Patch Links --
https://github.com/geany/geany/pull/2326.patchhttps://github.com/geany/geany/pull/2326.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2326
Hi,
This ones a bit simpler, basically when I press o (lowercase) in vimode, in geany it sends the cursor to the very beginning of the newline below, in vim it would respect the auto indent and put the cursor where it should be, just like hitting return at the end of a line in geany vimode.
The same happens with O (uppercase), although it is the line above, which is correct, just without the indent again.
I again offer my services if this is something people want.
Thanks,
Lukas
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/910
This PR adds a new API call to ```highlighting.c```:
``` C
const GeanyLexerStyle *highlighting_get_named_style(const gchar *named_style);
```
This shall enable plugins to query styles dedicated to plugin specific highlighting. Plugins could have their own styles with dedicated keys/names and instruct users to simply add them to a colorscheme. Another option would be a configuration setting in a plugin but then the setting is separated from the colorscheme which may result in bad readability.
Also see the discussion at https://github.com/geany/geany/issues/2331.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2336
-- Commit Summary --
* highlighting: added API call to query GeanyLexerStyle by name
-- File Changes --
M src/highlighting.c (24)
M src/highlighting.h (2)
M src/plugindata.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/2336.patchhttps://github.com/geany/geany/pull/2336.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/2336

--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/744