[Github-comments] Re: [geany/geany-plugins] Add bracket colors plugin (PR #1221)
@asifamin13, > Fixed a bug to address a case when nested brackets weren't getting their > color updated when their parent gets updated Looks like a good improvement. In the future, though, I would concentrate on just getting a minimal working version merged, then touch it up later in small, traceable iterations. To paraphrase [the famous saying of Valéry], a pull request is never finished; it's abandoned. [the famous saying of Valéry]: https://quoteinvestigator.com/2019/03/01/abandon -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1221#issuecomment-1499867052 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Filetype files documenting lexer property settings (Issue #3442)
See https://github.com/geany/geany/pull/3441#issuecomment-1493404204 -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3442#issuecomment-1493406299 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Add bracket colors plugin (PR #1221)
> ? why removed To get [your attention](https://github.com/geany/geany-plugins/pull/1241#issuecomment-1464731699), it seems. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1221#issuecomment-1465062083 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] RFC: Include Scintilla version in debug info (Discussion #3108)
There's a new upstream ticket on the version header issue: https://github.com/ScintillaOrg/lexilla/issues/142 -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3108#discussioncomment-5079723 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] TOML configuration language support (#1268)
> Well, now the creator of that needs to agree to change the license from > Notepad's to Lexilla's to upstream it. Nah, he can generate more sponsorship dollars by reserving the rights. I'd say he's earned it. Have you *seen* [how active][0] that project is? A regular beehive. [0]:https://github.com/zufuliu/notepad2/graphs/commit-activity -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1268#issuecomment-1417918831 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Add bracket colors plugin (PR #1221)
Perhaps the description and/or commit message should mention #1148? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1221#issuecomment-1416838077 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] TOML configuration language support (#1268)
> If "somebody" either: > > [ . . . ] > > b. created a new lexer Somebody downstream already has: https://github.com/zufuliu/notepad2/blob/main/scintilla/lexers/LexTOML.cxx -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1268#issuecomment-1416825806 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] [geany/geany-plugins] Outdated gpgme.m4 is blocking Debian package migration (Issue #1213)
According to [Debian's bug tracker]: > geany-plugins ships [an outdated version of gpgme.m4][0] which cannot handle > the transition from gpgme-config to [gpgrt-config]. Apparently the stale macros can be simply pruned out with no impact on the build: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1024483;filename=remove-outdated-gpgme.m4.diff;msg=5 But given the proposal to [drop geany-plugins from distribution][1], it seems Debian is expecting a dependency migration to libgpg-error-dev, with updated macros conforming to the gpgrt spec. There are examples around the Web that might be copied/adapted, e.g., - [GPGME](https://dev.gnupg.org/rMf9cbf2c8a839d2c3df20157cfe65b67a4b0bcb5a) - [libgpg-error (unofficial fork)](https://github.com/ShiftMediaProject/libgpg-error/blob/master/src/gpgrt.m4) The proper division of package maintenance roles is still mostly a mystery to me. This is just a heads-up, in case anything can be done from Geany's end. [Debian's bug tracker]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024483 [gpgrt-config]: https://manpages.debian.org/testing/libgpg-error-dev/gpgrt-config.1.en.html [0]: https://github.com/geany/geany-plugins/blob/0fd74d766f231e2aa84ca67af4da4773552eceb6/build/bundled/gpgme.m4#L1 [1]: https://tracker.debian.org/pkg/geany-plugins#:~:text=Version%201.38%2Bdfsg%2D1.1%20of%20geany%2Dplugins%20is%20marked%20for%20autoremoval%20from%20testing%20on%20Mon%2019%20Dec%202022. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1213 You are receiving this because you are subscribed to this thread. Message ID:
