In geany 1.37, and before, I can use the mouse's scrollwheel to go up and down the notebook tabs (using tab positions > editor > left)
In geany 1.38, I can't use the mousewheel to scroll tabs anymore.
Being able to use the scrollwheel is twofold useful: (A) if I'm constantly flipping between 2 files, I can point my mouse *anywhere* on the left tab pane, and scroll up or down a click, and mindlessly flip to my other file (even if I have many files open)
(B) if I have a great many files open (we all do, mkay?), so many that it goes off the page and makes little scroll buttons, flinging the scrollwheel is a great way to move yourself to the top or bottom, instead of mashing the scroll buttons. This is especially notable, because in 1.38, it uses a new version of GTK, where the tabs are much larger (I presume GTK wants to be touchscreen friendly??), and I can hold much fewer files on one screen, before having to overflow into a scroll
I'm on windows 10, if it makes a difference
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3191
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3191(a)github.com>
A. None of the dark schemes (bright text) view well with the current editing line which has a bright background highlighter. Am I missing something ?
B. The editor frame doesn't change color (as explained in another closed issue) because it is part of the GTK themes. But it does change if you ask Geany to invert ALL colors. In such a case, should not dark theme developers design their themes for inverted mode instead of normal mode?
--
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-themes/issues/40
This PR removes remaining deprecated symbols from `plugindata.h`. (See #3019 for overview of currently deprecated symbols.)
* GeanyFunctions
* GeanyKeyGroupInfo
* PluginFields
* PluginFlags
* PLUGIN_KEY_GROUP
* document_reload_file
* DOC_IDX(doc_ptr)
* DOC_IDX_VALID(doc_idx)
* GEANY_WINDOW_MINIMAL_HEIGHT
* GEANY_WINDOW_MINIMAL_WIDTH
The multiterm plugin, which currently doesn't compile because of GTK2-related dependencies, refers to the following symbols: PluginFlags, PluginFields, document_reload_file
The other symbols removed in this PR are not used by any known plugins.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3072
-- Commit Summary --
* Remove deprecated symbols: plugindata.h
-- File Changes --
M src/plugindata.h (73)
M src/pluginprivate.h (1)
M src/plugins.c (49)
-- Patch Links --
https://github.com/geany/geany/pull/3072.patchhttps://github.com/geany/geany/pull/3072.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3072
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3072(a)github.com>
Ok, I'm sure its a feature, but I have yet to locate the keybinding.
ctrl+shift+v , ctrl+shift+c are common copy paste commands in the linux terminal emulator, and I frequently inadvertently press them when copying and pasting between the terminal and geany. How can I unbind these key commands? whatever feature this is, isn't something I use, and the keybinding is too similar to something I use too frequently to have as a desired keybinding for something else. what is this feature, and how do I unbind this key combination?
--
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/2807
In this fragment of C++ code geany found:
main function only.
```C++
#include <iostream>
int main(int argc, char **argv)
{
return 0;
}
extern "C"
{
void f() {}
}
```
Geany 1.38 (build 2021-09-01 or later)
Used GTK+ v3.24.30 and GLib v2.70.0 runtime libs
#349
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3189
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3189(a)github.com>
I tested Geany with valgrind to make sure #3185 didn't introduce any memory leaks (it seems it didn't) and noticed this leak in the docbook parser (which we maintain by ourselves so no upstream patch needed). I'll merge this in a few days unless there are objections.
There are also leaks in Fortran (fixed upstream) and VHDL (different parser upstream) parsers which will get fixed once we merge the upstream versions.
For (my) future reference, I used valgrind with these parameters:
```
G_SLICE=always-malloc G_DEBUG=gc-friendly:resident-modules ./libtool --mode=execute valgrind --tool=memcheck --leak-check=full --leak-resolution=high --log-file=vgdump --suppressions=/usr/share/glib-2.0/valgrind/glib.supp src/geany
```
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3187
-- Commit Summary --
* Fix docbook parser memory leak
-- File Changes --
M ctags/parsers/geany_docbook.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/3187.patchhttps://github.com/geany/geany/pull/3187.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3187
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3187(a)github.com>
I don't know why this happens with Geany. but the input function shows up as an invalid syntax in the terminal for some reason.
I tried the same code with Visual studio code and it executed just fine.
I'll show a screenshot.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3188
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3188(a)github.com>
When editing a multi-part project (like a Python project with several modules), I frequently forget to save a module's file before running the main program again. So I have to either ctl-shift-S, then retry, or go back to the changed tab, save, back to the main, and try again.
Would it be difficult to implement a way, such that, on execute, all changed tabs get saved? I considered:
- Adding an option in the build command lines
- Implement a %-variable (say %! or so) which does the saving, and can be included in the build command
Or maybe I'm just missing something?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3186
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3186(a)github.com>