@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,
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:
> ? 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
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
> 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.
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:
> 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:
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: