Now that a new enough GLib is available the signal can be handled cleanly on the main loop using the GSource for Unix signals. This replaces the illegal SIGTERM handling that was disabled in
fbb89f523af47b35e238678d348cfa98e56c760a.
In the future, we might also like to handle `SIGPIPE` which was ignored in cc511a78d80fde742e1794c32b2738ae8ddd4792 to log the error instead of just ignoring it (or handling `write()` failures at their source).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1255
-- Commit Summary --
* Re-enable SIGTERM handling
-- File Changes --
M src/libmain.c (21)
-- Patch Links --
https://github.com/geany/geany/pull/1255.patchhttps://github.com/geany/geany/pull/1255.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/1255
This is to get the ball rolling on the [Port to GSettings project](https://github.com/geany/geany/projects/1).
See individual commit messages for more details.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1257
-- Commit Summary --
* Add initial GSettings support
* Change 'sidebar_pos' to use GSettings
* Port "fullscreen" preference to GSettings
* Port "sidebar_visible" preference to GSettings
* Port "msgwindow_visible" preference to GSettings
* Port "statusbar_visible" preference to GSettings
* Port "sidebar_*_visible" preferences to GSettings
-- File Changes --
M configure.ac (2)
M data/Makefile.am (4)
A data/org.geany.Settings.gschema.xml (53)
M po/POTFILES.in (1)
M src/Makefile.am (2)
M src/build.c (11)
M src/callbacks.c (70)
M src/keybindings.c (5)
M src/keyfile.c (29)
M src/libmain.c (33)
M src/msgwindow.c (25)
M src/msgwindow.h (2)
M src/prefs.c (44)
A src/settings.c (77)
A src/settings.h (35)
M src/sidebar.c (46)
M src/sidebar.h (2)
M src/ui_utils.c (63)
M src/ui_utils.h (13)
M src/vte.c (5)
-- Patch Links --
https://github.com/geany/geany/pull/1257.patchhttps://github.com/geany/geany/pull/1257.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/1257
For some reason "project-save" isn't emitted when closing project - see
write_config(FALSE) in project_close(). This means that in this case
plugins cannot save their configuration into the config file. This doesn't
even correspond to the documentation of the signal
"Sent when a project is saved (happens when the project is created, the
properties dialog is closed or Geany is exited)"
as the signal isnt emitted when exiting Geany because at this point Geany
closes the project.
The comment seems to indicate that the reason is that "project-save"
shouldn't be emitted when "project-close" is emitted but I don't see any
reason why.
Bump API so plugins can rely on the changed behavior.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1400
-- Commit Summary --
* Always emit the project-save signal when writing project file
-- File Changes --
M src/plugindata.h (2)
M src/project.c (20)
-- Patch Links --
https://github.com/geany/geany/pull/1400.patchhttps://github.com/geany/geany/pull/1400.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/1400
This allows plugins to reload keybindings later during their execution.
For more info see the comment in the commit.
---
I'm working on a plugin which is a more universal version of the current GeanyMiniscript plugins - users will be able to write custom scripts which will be executed and depending on the configuration the output will replace current document or selection or be inserted at current position or shown in new window etc. Users will be able to create new scripts (and remove existing). Each script will be keybindingable and since scripts can be removed or added, keybindings have to reload which isn't currently possible because keybindings_load_keyfile() isn't public and because of #1426.
(The plugin is in a VERY early stage of development and will likely not come out soon.)
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1430
-- Commit Summary --
* Export keybindings_load_keyfile() for plugins
-- File Changes --
M src/keybindings.c (9)
M src/keybindings.h (4)
M src/plugindata.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/1430.patchhttps://github.com/geany/geany/pull/1430.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/1430
Bash lists with only one string item are not applying syntax highlighting.
It worked correctly with an older version of Geany, but I cannot say when this regression was introduced.
Example:
```
#!/bin/bash
var1=('foo')
var2=('foo: works')
var3=('foo', 'bar')
```
Expected syntax highlighting:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packa…
See line 13, 16-20, 22.
System information:
* Arch Linux
* Geany 1.2.9
--
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/issues/1308
![selection_145](https://cloud.githubusercontent.com/assets/3821217/22738305/f05ea8ce-ee17-11e6-816c-ba29a0b56ae5.jpg)
What's wrong here? I expected the file to be auto reloaded now.
--
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/issues/1388
An inconvenience:
1. Configure some keybindings for Next Message, Switch to Messages, and Switch to Editor.
2. Do something (e.g. find in files) to populate the messages pane.
3. Press the Next Message key. The next message is selected (highlighted).
4. Press the Switch to Messages key, then press the Switch to Editor key.
5. Press the Next Message key again. The next message is again selected.
6. Press the Switch to Messages key again. You will see that the GTK+ keyboard focus is not on the currently selected (highlighted) message, but rather still on the message that was selected back in step 3.
Here’s a screenshot (notice how the selected message is not the same as the one with the focus box around it):
![geany-focus](https://cloud.githubusercontent.com/assets/300211/16467792/8ef63c30-3e51-11e6-90f2-720e7aab89cb.png)
Why is this a problem? — Because if I switch to the messages pane and use the up/down keys to navigate around the list (e.g. when I want to skip a bunch of messages), navigation starts from the focus, not from the selection. In effect, I am thrown back to some previous point and have to find the “current” message on my own.
---
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/issues/1098