* It looks either a bit confusing or to have some bugs (without having investigated deeply, it did things I didn't understand);
* It marks all lines when reloading a file (instead of resetting to a blank slate);
* If marker margin is not visible, it can render the editor unreadable with the default settings;
* I don't see any obvious use case given its current behavior that warrants a so visible feature by default;
* I don't think the feature is obvious at first glance, which could easily lead users to wonder what that line is about. It also looks similar to other editor's VCS commit status indicator (including git-changebar Geany plugin) display, yet behaves very differently, possibly increasing confusion.
So for now, I think it's better to have it disabled by default.
See also discussion starting at https://github.com/geany/geany/pull/3551#issuecomment-1751809855
Opinions @kugel- @eht16 @techee @elextr @ntrel and everyone else?
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3591
-- Commit Summary --
* Do not enable Scintilla's Change History by default
-- File Changes --
M src/keyfile.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/3591.patchhttps://github.com/geany/geany/pull/3591.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3591
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3591(a)github.com>
There was a mistake in my fix for wayland popups, as @b4n correctly noticed in https://github.com/geany/geany/pull/3011#issuecomment-1279825987. The problem was that the "Go to symbol definition" did not open the popup in correct location.
This PR contains two commits:
- First fixes the problem
- Second removes support for prehistoric versions of GTK
The first commit might be used separately, but I have to openly admit that the #ifdefed code is not tested, because I couldn't find any system in my reach with old enough GTK. The second commit should not be merged until GTK 3.24 is officially required for Geany. But I guess that it should not be a problem, this PR can probably wait untill then, since no one noticed the bug for a month.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3316
-- Commit Summary --
* Fix go to symbol definition popup location
* Drop support for GTK 3.21 and older
-- File Changes --
M src/callbacks.c (2)
M src/editor.c (2)
M src/msgwindow.c (9)
M src/notebook.c (8)
M src/plugins.c (3)
M src/prefs.c (21)
M src/sidebar.c (8)
M src/symbols.c (91)
M src/ui_utils.c (26)
M src/ui_utils.h (2)
M src/vte.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/3316.patchhttps://github.com/geany/geany/pull/3316.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3316
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3316(a)github.com>
I am using Geany in Linux Mint and Kubuntu, so I comfortable with KDE and GTK. This problem is identical in both and has nothing to do with a selected color scheme. Dark system themes are not always preferred.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3601
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3601(a)github.com>
Yeah, done now.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-osx/commit/c79e60f1cc0c25106ab803b2b4c9e6192…
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-osx/commit/c79e60f1cc0c25106ab803b2b4c9e61926ce12fa/130019403(a)github.com>
I have been attempting to install the webhelper plugin, i first tried to install it i tried building from source, this work after a while however the webhelper plugin was missing. i tried installing it through dnf as i am on fedora but every plugin, BUT webelper was available.
i noticed that someone else had the same problem a me, in a forum:
https://forums.linuxmint.com/viewtopic.php?t=350114
> it depends on deprecated webkitgtk, so Debian maintainers [disabled](https://salsa.debian.org/geany-team/geany-plugins/-/commits/maste… it. I guess it will be so until it's ported to webkit2gtk.
When i try to compile it from source i get the message:
```
checking for WEBHELPER... no
configure: error: Package requirements (gtk+-3.0 >= 2.16
glib-2.0 >= 2.22
gio-2.0 >= 2.18
gdk-pixbuf-2.0 >= 2.0
webkitgtk-3.0 >= 1.1.18
gthread-2.0) were not met:
Package 'webkitgtk-3.0', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables WEBHELPER_CFLAGS
and WEBHELPER_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
```
i installed all of these and still get the same errors.
is there any solution?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1269
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1269(a)github.com>
Hi, Dear experts:\
  I'm glad to be able to use this lightweight IDE on Win10 ):\
  I'm very interested in it and hope to expand its functionality, so I'm first try to build geany & geany-plugins on windows, following https://wiki.geany.org/howtos/win32/msys2 titles of **Initial Setup**&**Geany Compilation**&**Geany-Plugins Compilation**.\
  After I finished compiling, I was able to run **geany.exe**, but I couldn't find any plugins through the plugin gear manager. I checked the compiled product, it was found that the compiled products of geary plugin are both **. a** and **. la**. Then I referred to **Creating a GTK runtime bundle** try to fix this problem, but it is not work. \
  After that, I tried to directly install gear and gear plugin using the installation package linked on the official website(https://download.geany.org/geany-1.38_setup.exehttps://plugins.geany.org/geany-plugins/geany-plugins-1.38_setup.exe), I found that all plugins are basically **. dll** or **. dll. a** suffixes.\
  What should I do to solve this problem or how did you compile and use geany and geany-plugin under Win10？
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3532
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3532(a)github.com>
I'm afraid it's too late since the translation string freeze already happened. But we should finally review and merge it after 2.0.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1221#issuecomment-1763325064
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1221/c1763325064(a)github.com>
Sorry for being late, I just thought this might be also good for the dark variant of the theme?
Currently it uses the large statusbar.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-osx/commit/c79e60f1cc0c25106ab803b2b4c9e6192…
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-osx/commit/c79e60f1cc0c25106ab803b2b4c9e61926ce12fa/130012991(a)github.com>
This PR adds a patch that could be applied during the Windows build to make the Prof-Gnome theme look more native. It:
- sets #000000 as the text color
- decreases statusbar height by 6px
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-osx/pull/35
-- Commit Summary --
* Add a patch with Windows-specific changes to Prof-Gnome
-- File Changes --
A prof_gnome_windows_changes.patch (41)
-- Patch Links --
https://github.com/geany/geany-osx/pull/35.patchhttps://github.com/geany/geany-osx/pull/35.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-osx/pull/35
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-osx/pull/35(a)github.com>