The "Language Files" option of the Windows' installer only disables language files for Geany, but not for Gtk runtime. As a result, the installation takes 68.7 MB, 33.5 MB (49%) of which are MO files of Gtk in "share/locale" folder. However, the real issue is not the disk space but the fact that the interface becomes partially translated.
The same problem is with the installer for plugins.
--
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/2090
Two consecutive "go to matching brace" commands have to return us to the original position. After we moved to the matching brace, we still should see the same brace pair highlighted. All Scintilla-based editors have the problem. Scintilla doesn't necessarily return us to the initial position after the subsequent matching brace jumps. After the first jump Scintilla often highlights nearby brace pair. It is so because Scintilla attempts to place the cursor following to outside or inside braces logic. However, when the cursor is between two braces, Scintilla highlights only the first, left brace.
I will provide with two examples. (bold+italic parenthesis indicate the highlighted braces. The exclamation sign indicates the cursor position. )
First example: ( )( )
Place the cursor after the last brace:
( )_**( )!**_
do twice "go to matching brace" and we see the cursor before the fist brace.
**_!( )_**( )
Second example: (((( f1+1 )^f2)+( f3+1 ))^f4)
Place the cursor after the second brace.
(**_(!_**(( f1+1 )^f2)+( f3+1 )**_)_**^f4)
do twice "go to matching brace" and we see where the cursor is .
(((( f1+1 )^f2)+**_!(_** f3+1 **_)_**)^f4)
People who are used to work with other editors are confused. As a workaround, I made a LUA script that goes to matching brace and always keeps the same braces highlighted. (https://github.com/dyura/LUA-scripts-for-text-editors/blob/master/Geany/GoT…)
At the same time, I think that this problem should be solved at the project level.
--
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/1998
Hi, this is actually an enhancement request for pohelper.
When I open the "Translation statistics" dialog, I can't continue editing the file I have open in the editor.
I'd like to be able to keep editing the po file and view the stats at the same time.
Thank you, and kind regards,
Lucas
--
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/843
This should fix #808.
The approach here is to try and have the Python callback return value be used as the C one is. I'm not totally sure how compatible that is, but IIUC if a Python function doesn't explicitly return it returns None, which should (I guess) fail the `PyObject_IsTrue()` check.
I did *not* test this *at all*: I didn't even try to build it (thanks to a crappy Internet connection tonight, I didn't wait long enough to fetch the dependencies). This PR should be reviewed as what it is: an attempt at a fix by a guy that doesn't know neither the API nor the plugin :)
However, this should also fix a leak as the return value should likely be `DECREF`'d in any case.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/809
-- Commit Summary --
* geanypy: Use Python callback return value for keybindings return value
-- File Changes --
M geanypy/src/geanypy-keybindings.c (8)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/809.patchhttps://github.com/geany/geany-plugins/pull/809.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/809
2 changes to make a11y quite a bit faster especially when performing bulk search & replace.
The first commit makes use of the character offset cache when performing reverse-lookup, e.g. when we need to convert a position given by the a11y layer to one understood by Scintilla.
The second avoids clearing the cache when it gets invalidated, and instead updates it to be valid right away. This avoids potentially costly re-computation of the cache that becomes problematic when we often need a position near the end of the file but keep invalidating everything after lines near the start. This happens especially when performing bulk search & replace with the cursor near the end. This gives a slightly higher cost at invalidating the cache (that now updates it based on a known delta), but a lot less when it's content is needed again.
Fixes #2092.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2097
-- Commit Summary --
* scintilla: GTK: a11y: Optimize byte to character offset conversion
* scintilla: GTK: a11y: Avoid clearing cache when possible
-- File Changes --
M scintilla/gtk/ScintillaGTKAccessible.cxx (15)
M scintilla/gtk/ScintillaGTKAccessible.h (14)
-- Patch Links --
https://github.com/geany/geany/pull/2097.patchhttps://github.com/geany/geany/pull/2097.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/2097