WrapEarnPass left a comment (geany/geany-plugins#1570) The positive consequences would be I get the fixes for geanylua and the other plugins from master for my 2.1 system install, without having to actually build the unstable 2.2 as well. Limiting the scope of changes I have to account for in testing. I.e. is my plugin breaking because I failed to build geany2-2, or is it breaking because geany2-2 has a bug.
CC-BY-NC On Mon, Jul 13, 2026, 8:09 AM Skif-off ***@***.***> wrote: > *Skif-off* left a comment (geany/geany-plugins#1570) > <https://github.com/geany/geany-plugins/issues/1570#issuecomment-4957773821> > > Plenty of plugins, which all build in the existing geany environment, > definitively above GTK 3.0.0, check for it anyway. > > At least some of these checks are a legacy of the GTK2 -> GTK3 transition > and of course will be removed in the future. > > And, as the file is breaking in this build, for only this plugin, and for > no other plugins > > This is not true, you saw one problem at this particular moment in time, > but it is not the first and not the last similar problem. > > geanylua/glspi_keycmd.h is checked in. It is not regenerating on build. Is > a build task missing? > > In this case, full automation can cause problems, so it is more practical > to use mk-keytab.lua when making a corresponding change in Geany or > simply before a release. For example > <https://github.com/geany/geany/pull/4502>. > > I'm probably a bit stupid :))) > As I understand it, plugins interact with Geany and use functions from the > Geany library (for example, instead of directly interacting with > Scintilla), the versions of Scintilla and Universal Ctags used by Geany > also matter: so, we have several places where something might not work at a > specific point in time between releases. And it's logical that the plugin > version matches the Geany version (and this is not an unique example). > I don't understand what positive consequences this > > Now it builds on geany2-1, and 2-2, without having to make a hard > dependency on geany >= 2.2 > > has :) > > — > Reply to this email directly, view it on GitHub > <https://github.com/geany/geany-plugins/issues/1570?email_source=notifications&email_token=CGAYOAWV2ORTL7JXK5SQ6NL5ETGPBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVG43TOMZYGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4957773821>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/CGAYOAQMBQ2MFL4VCJDO6WD5ETGPBAVCNFSNUABDKJSXA33TNF2G64TZHMZDKOJXGY2DQO2JONZXKZJ3GQ3DOMBSHA2TOOBRUF3AE> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > <https://github.com/notifications/mobile/ios/CGAYOATKUQ5Z422ZMK7LTZD5ETGPBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVG43TOMZYGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> > and Android > <https://github.com/notifications/mobile/android/CGAYOAVIL3EKIOGHOQE54IL5ETGPBA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVG43TOMZYGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. > Download it today! > You are receiving this because you authored the thread.Message ID: > ***@***.***> > -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1570#issuecomment-4957855717 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/issues/1570/[email protected]>
