This PR expands the zoom range of the zoom keybindings.
* Zooming via scroll wheel is unaffected (-10 to +20).
* Zoom in is "unlimited". (But everyone stops zooming eventually.)
* Zoom out stops when the font size reaches 2pt (limited by scintilla). Current behavior is to zoom out to -10 even when the font size doesn't change. So for a base font size of 10pt, the current behavior has the last three zoom levels (-8, -9, -10) set at 2pt. This PR stops at -8. But if the base font size is 16pt, zoom out with this PR continues to -14.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2955
-- Commit Summary --
* <a href="https://github.com/geany/geany/pull/2955/commits/58dfdd068b7e273d32b9062dd3…">Expand range of zoom keybindings</a>
-- File Changes --
M src/sciwrappers.c (16)
-- Patch Links --
https://github.com/geany/geany/pull/2955.patchhttps://github.com/geany/geany/pull/2955.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/2955
is there a plugin in Geany capable of highlighting codes to display HEX and RGB colors with an appropriate marker? or is it possible to do this in the config syntax highlighting?
--
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/1130
I have compiled Geany and all Geany plugins using gcc 8.4 on an NVIDIA Jetson Nano. The Jetson runs Nvidia's "Linux for Tegra", based on Ubuntu 18.04. Everything compiled and linked without errors. I've installed my locally-built Geany and plugins, using the "make install" step, and they both appeared to succeed. Geany launches normally. However, the Debugger plugin is not listed under Tools -> Plugin Manager. I do see a "debugger.so" and "debugger.la" under /usr/local/lib/geany. The Jetson Nano does have gdb installed and I can debug executables "the hard way".
I see lots of foo on various forums about the Debugger plugin having been removed from various Debian distros. The suggestion is to build Geany 1.37 and its plugins from source, which I have done. So ... what else am I missing? Is there some other missing dependency? How can I further debug why the Debugger plugin is not listed in Geany's Plugin Manager? The Jetson Nano is a fairly common development box, very similar to a Raspberry Pi. Suggestions welcome.
--
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/1116
In trying to NOT have my quotation marks and parentheses auto-close, I discovered that both the preferences and the plugins have auto-close options.
If you have both auto-close options on for paretheses, square brackets, and brackets, it still only produces one complementary character. However, if you have both auto-close options on for quotation marks, single or double, it produces a second complementary character, making three in total (that is, """). This doesn't make sense.
I'm using Geany 1.36. I checked the release notes of all the versions after that up to 1.8 and there has been no reported fix for this problem, so I assume it hasn't been noticed.
--
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/1127
The title more or less scoops the entire problem. Anytime I (accidentally) use `Ctrl+Shift+V`, Geany crashes with _Segmentation fault_.
**Versions:**
* Geany 1.38
* MATE 1.26.0
* GTK3 3.24.30
Also, the crash doesn't happen on a Windows system. I suspect this might come up in the discussion, but I'm not using any additional clipboard managers, except for what MATE does with the clipboard by default.
--
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/2980
In the preferences, there are check boxes labeled "Save window size" and "Save window position". They set `prefs.save_wingeom` and `prefs.save_winpos`, which are used in [libmain.c](https://github.com/geany/geany/blob/04566236d3f9811d55d6c7bcc492… to control whether the window size and position are *restored*.
These settings should control *only* whether (new) sizes and positions are *saved*. Whatever is *already* saved should be restored.
--
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/2978
Geany built from git. GTK+ v3.24.30, GLib v2.68.4.
Steps to reproduce:
1. Maximize Geany.
2. Hide message window.
3. Close Geany.
4. Restart Geany.
5. Unmaximize Geany.
6. Reshow message window. Appears to fail because message window has zero height. Can be resized to former height.
Notes:
* Message window is at the bottom of the window. Have not tested, but probably not an issue if message window is at the top or sides.
* Potential solution: In the config file, The message window position is saved. Instead, the message window size should be saved, and the position calculated based on which side it's on.
* Potential solution: Calculating position is complicated by the visibility and size of various components. Saving the position for maximized and normal states separately would also prevent this problem.
--
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/2977
Geany built from git. GTK+ v3.24.30, GLib v2.68.4.
Steps to reproduce:
1. Geany in normal window mode. Close. Reopen. Window is restored to previous size. (as expected)
2. Toggle between maximized and normal states. Normal window size does not change. (as expected)
3. Maximize Geany. Close. Reopen. Window is restored to maximized state. (as expected)
4. Toggle to normal state. Window is shorter than previously (on KDE Plasma). Expected is for the previous size of the normal state to be restored.
Notes:
* This occurs regardless of whether the message window and sidebar are visible.
* The behavior described occurs on KDE plasma with 2x display scaling enabled. On XFCE with no display scaling, the window is larger than expected.
* Potential solution: The geometry setting appears to have a flag to indicate the maximized state. There is no need to change the width/height when the window is maximized.
--
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/2976