> 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](https://quoteinvestigator.com/2019/03/01/abandon), a pull request is never finished; it's abandoned.
Understood. What it currently on this branch is the "minimal working version". There is one more feature I want to add (user defined colors via preferences menu/config file). I'm working on this now, hopefully to be finished this week. I'll keep that on a different commit
> Wise(ish) words, and its corollary, 'Every time a PR changes "somebody" has to re-check it and re-test it, and eventually "somebody" gets bored' :-)
I'm fine being that "somebody" haha I've had fun writing this plugin.
Do new plugin PRs getting pulled in on the next geany-plugins release?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1221#issuecomment-1513502773
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1221/c1513502773(a)github.com>
or double click, or any combination with key
Seems to not exist in menu-click, so how to do it the simplest way, or just this'd be a feature request ?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3464
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3464(a)github.com>
> OS: Windows 10 64-bit
Environment: MSYS2/MinGW-w64
Geany source: f0e3ee273e67387f85506ea629b9dbe34d47b8ca
My compiler complains that the `alloca.h` header is missing.
```
FAILED: libregex.a.p/ctags_gnu_regex_regex.c.obj
"cc" "-Ilibregex.a.p" "-I." "-I.." "-I../ctags/fnmatch" "-fdiagnostics-color=always" "-D_FILE_OFFSET_BITS=64" "-Wall" "-Winvalid-pch" "-std=c11" "-O3
" "-DHAVE_CONFIG_H=1" "-O2" "-D__USE_GNU" -MD -MQ libregex.a.p/ctags_gnu_regex_regex.c.obj -MF "libregex.a.p/ctags_gnu_regex_regex.c.obj.d" -o libreg
ex.a.p/ctags_gnu_regex_regex.c.obj "-c" ../ctags/gnu_regex/regex.c
In file included from ../ctags/gnu_regex/regex.c:61:
../ctags/gnu_regex/regex_internal.h:424:11: fatal error: alloca.h: No such file or directory
424 | # include <alloca.h>
| ^~~~~~~~~~
compilation terminated.
```
According to [this answer on SO](https://stackoverflow.com/a/58286937/4677917), `alloca.h` does not exist in Windows & should be replaced with `malloh.h`.
I haven't tested it yet. Wanted to get the report posted.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3437
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3437(a)github.com>
#1017 continuation, new (last) attempt.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1752
-- Commit Summary --
* Add AutoIt syntax highlighting and Ctags parser for AutoIt
-- File Changes --
M ctags/Makefile.am (1)
M ctags/main/parsers.h (3)
A ctags/parsers/autoit.c (121)
M data/Makefile.am (3)
A data/filedefs/filetypes.autoit (72)
M data/filetype_extensions.conf (1)
M scintilla/Makefile.am (1)
A scintilla/lexers/LexAU3.cxx (910)
M scintilla/scintilla_changes.patch (2)
M scintilla/src/Catalogue.cxx (1)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (9)
M src/highlightingmappings.h (35)
M src/symbols.c (8)
M src/tagmanager/tm_parser.c (5)
M src/tagmanager/tm_parser.h (1)
M tests/ctags/Makefile.am (1)
A tests/ctags/simple.au3 (32)
A tests/ctags/simple.au3.tags (5)
-- Patch Links --
https://github.com/geany/geany/pull/1752.patchhttps://github.com/geany/geany/pull/1752.diff
--
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/pull/1752
I just noticed in the CI workflow for the "traditional" Autotools based jobs, we did not specify "-j" for parallel job execution for the main "make" call to build all the sources.
We did however for "make check" and "make distcheck".
If there is no reason for not using "-j 2", this PR adds it and potentially speeds up the CI jobs a bit.
For Meson, as far as I understood "ninja" uses parallel execution by default with the number of CPU cores available.
For Mingw64, I just enabled "-j $JOBS" if it is set (957da21ddfc6e9e00f1a7b208d55e7ed3f7ebe20).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3432
-- Commit Summary --
* CI: Define JOBS environment variable and use it for make
-- File Changes --
M .github/workflows/build.yml (7)
-- Patch Links --
https://github.com/geany/geany/pull/3432.patchhttps://github.com/geany/geany/pull/3432.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3432
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3432(a)github.com>
The weekly rebuild of the CI container image for the Mingw64 builds works fine.
But the previous image versions are kept as untagged images in the container registry.
This workflow should remove all untagged image versions except that last five ones.
It is schedules weekly two hours after the image build workflow.
I'm not completely sure if it works out of the box, let's see on its first run :).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/infrastructure/pull/9
-- Commit Summary --
* CI: Add workflow to cleanup old untagged CI container image versions
-- File Changes --
A .github/workflows/package-cleanup.yml (30)
-- Patch Links --
https://github.com/geany/infrastructure/pull/9.patchhttps://github.com/geany/infrastructure/pull/9.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/infrastructure/pull/9
You are receiving this because you are subscribed to this thread.
Message ID: <geany/infrastructure/pull/9(a)github.com>
It would be nice to have a feature to collapse all tags of xml text (or other code) to, say level 1 or level 2.
--
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/3041
Since Lexilla only code-documents the available properties its hard for users to find what they have. It would be useful if the filetype files listed all the properties, either set to Lexilla default, or commented out.
Probably doesn't have to happen all at once, but as filetypes files are touched for other reasons.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3442
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3442(a)github.com>