The patch adds a new keybinding action for undoing hunks. When cursor is
placed at a line with a diff and the keybinding is invoked, the
corresponding hunk is undone.
To get the previous contents at the given position, a temporary Scintilla
instance is used into which the previous state of the document is loaded
and the corresponding text from the previous state of the document is
extracted. This temporary Scintilla object is then destroyed.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/531
-- Commit Summary --
* git-changebar: Add the possibility to undo hunk at cursor position
-- File Changes --
M git-changebar/src/gcb-plugin.c (135)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/531.patchhttps://github.com/geany/geany-plugins/pull/531.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-plugins/pull/531
This is a wrapper around `tm_get_real_path()` but is in a more suitable namespace/module.
I think it makes more sense like this. I typically dislike adding general-purpose functions to the API, but since Glib doesn't provide any equivalent, it really is useful.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1224
-- Commit Summary --
* Add utils_get_real_path() and use it
-- File Changes --
M src/app.h (2)
M src/document.c (8)
M src/libmain.c (2)
M src/plugindata.h (2)
M src/tagmanager/tm_source_file.c (2)
M src/utils.c (29)
M src/utils.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/1224.patchhttps://github.com/geany/geany/pull/1224.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/1224
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
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