[Github-comments] Re: [geany/geany] Thumbs up hunt (Issue #3938)

> @rdipardo has indicated that the Kotlin parser is ok for their usage ... Not that I recall. This is probably a reference to @dolik-rce's pull request comment: - https://github.com/geany/geany/pull/3034#issuecomment-987693940 -- Reply to this email directly or view it on GitHub: https://gith

[Github-comments] Re: [geany/geany] Thumbs up hunt (Issue #3938)

> As I keep saying it is not good software design to compile everything in, > making all users, even those on Raspberry Pi, pay for lexers and parsers that > are not used by them. Honest question here: would they pay in binary size or in memory consumption? I know that Notepad++ statically buil

[Github-comments] Re: [geany/geany] GCode support (Issue #3879)

"First-class" syntaxing would have to be implemented by Lexilla (Geany's lexing library). See: - -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3879#issuecomment-2143271531 You are receiving this

[Github-comments] Re: [geany/geany] Use GtkFileChooserNative for opening files on Windows and macOS (PR #3861)

> Windows 10/11 feedback would be great So far so good on a stock Win 10 (22H2) VM with native dark mode active (i.e. `AppsUseLightTheme` == `0`):1. https://github.com/geany/geany/assets/59004801/ef76157a-d5ae-4111-b147-ce6a4ce91945";> > Also I presume the native dialogs are themed by the platf

[Github-comments] Re: [geany/geany] Cannot install (Issue #3852)

@ineuw > There doesn't seem to be a simple direct installation method for users with > limited knowledge, like myself. Here is a copy-and-paste-able installation script (assuming you don't care about the API documentation), suitable even for [CI/CD deployments](https://github.com/rdipardo/fpg

[Github-comments] Re: [geany/geany] Change bar all green after reload (Issue #3824)

> Change bar all green after reload Known Scintilla defect: > An issue that has appeared with change markers is that SciTE's Revert command > leads to the whole document getting a green change mark as revert just > reloads each byte of the file. Since its useful to undo to before the rever

[Github-comments] Re: [geany/geany] Add CodeQL Analysis workflow (PR #3769)

@andy5995 > ... an invite to be a collaborator. You could also just open a PR in your fork from the branch with the CodeQL workflow in it. If an alert doesn't appear automatically, there should be an option to publish it. -- Reply to this email directly or view it on GitHub: https://github.co

[Github-comments] Re: [geany/geany] Add CodeQL Analysis workflow (PR #3769)

> Erm, the link doesn't work. That's because: > [y]ou need write permission to view a summary of all the alerts for a > repository on the **Security** tab. > >

[Github-comments] Re: [geany/geany] MSYS2 package for Geany (Issue #3756)

> Geany source code will not built out of the box on MSYS2. See https://github.com/geany/infrastructure/tree/master/builders#windows-mingw64-build -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3756#issuecomment-1935449519 You are receiving this beca

[Github-comments] Re: [geany/geany-plugins] Markdown preview shows nothing (Issue #1302)

> Ok, that indeed looks like its the webkit2gtk bug. So you only need to wait > for your distro to provide the fixed version. Debian-based distros may not be so lucky until this RC bug is resolved: Basically what @jbicha [said already](https://github.com/geany

[Github-comments] Re: [geany/geany] A picture says more than a 1000 words... (Discussion #3746)

Sounds like one of those aggregators that decorate listings with the repository's [social media preview image][0], which `geany/geany` doesn't have . . . yet? https://github.com/geany/geany/assets/59004801/ebd829a9-ce56-4408-b4a9-86f90752f735"; width="400"/> [0]: https://docs.github.com/en/

[Github-comments] Re: [geany/geany] File Encoding Errors (Discussion #3731)

> There is no other way of passing the information of what the file encoding is > to Java AFAIK (unless there is a command line option you can add) export JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8 This resolved [a similar issue][0] for a Windows user, *mutatis mutandis*. JDK toolchain binarie

[Github-comments] Re: [geany/geany] Geany 4.0, the GTK4 edition (and more) (Discussion #3675)

> I hope GTK3 will be still supported for a long time. You're [not alone][0], so keep hoping! > The GTK 3 ABI is finally a stable target, and it’s still pre-installed in > most distributions because lots of built-in apps haven’t upgraded yet. If we > can get a sufficient number of binary apps d

[Github-comments] Re: [geany/geany] Is it possible to manage the text at the line indicated? (Discussion #3718)

@ineuw Does this GIF illustrate the kind of feature you're asking about?  > [!Note] > The demo assumes the > [`textwidth`](https://vimhelp.org/options.txt.html#%27tw%27) (`tw`) and >

[Github-comments] Re: [geany/geany] Is it possible to manage the text at the line indicated? (Discussion #3718)

I'm not sure either, but I think the question could be rephrased as: > Can the column boundary marker actually enforce the column limit, instead of > just visually indicating where a break should ideally occur? So, imagine the marker had the same effect as manually narrowing the main window's

[Github-comments] [geany/geany] 🎉 Geany writeup in The Register 🎉 (Discussion #3712)

Today the [The Register](https://www.theregister.com) published a small profile of the Geany project to mark the 2.0 release: ["Veteran editors Notepad++ and Geany hit milestone versions"](https://www.theregister.com/2023/12/06/veteran_editors_notepad_and_geany) -- Reply to this email directl

[Github-comments] Re: [geany/geany] Update Pascal filedef and extension mappings (PR #3694)

> Finally another filetype file converted to the "new" build, its only been 13 > years Mass migrations to a new spec are seldom worth the effort, and there's always somebody who prefers the old way. As for the long neglect of Pascal, it's no surprise when the Lazarus IDE has been free and cros

[Github-comments] Re: [geany/geany] Update Pascal filedef and extension mappings (PR #3694)

Check 9ca281b02 to see if I have the right idea. Since Pascal compilers are single-pass, the nearest equivalent to a strict compile command seems to be [the option to skip the linker](https://www.freepascal.org/docs-html/user/userap1.html) (`-s`). A new side-effect will be the generation of a

[Github-comments] Re: [geany/geany] Update Pascal filedef and extension mappings (PR #3694)

@rdipardo pushed 1 commit. 9ca281b02921083ab1e8b7680865737592192ef1 Replace obsolete [build_settings] with [build-menu] -- View it on GitHub: https://github.com/geany/geany/pull/3694/files/2e72e8dd520810e809509537adac6b1238a594ab..9ca281b02921083ab1e8b7680865737592192ef1 You are receiving this

[Github-comments] [geany/geany] Update Pascal filedef and extension mappings (PR #3694)

filetypes.pascal - add line comments - pair the 'fpc' compile command with another common Free Pascal utility [^1], 'instantfpc', to build and run the current file in a single step filetype_extensions.conf - add Lazarus project files (*.lpr) [^1]: https://wiki.freepascal.

[Github-comments] Re: [geany/geany-plugins] avoid parsing opened files when loading project #1289 (PR #1290)

@rdipardo commented on this pull request. > @@ -276,13 +276,24 @@ static GeanyFiletype *filetypes_detect(const gchar > *utf8_filename) } +static gboolean string_exists_in_array(gchar **array, gchar *str) { > I'm pretty sure this function already exists in glib or somewhere... Perhaps you

[Github-comments] Re: [geany/geany] Add Prolog filetype support (PR #3171)

@techee > Yep, done in #3651 Except for the "ticklist of filetypes to add", or *task*list, which GitHub [can automatically generate][0] for list items with a "tick box" beside them, e.g. ~~~markdown - [ ] Needs a tick - [X] Ticked! ~~~ [0]: https://docs.github.com/en/issues/managing-your-ta

[Github-comments] Re: [geany/geany] Convert JSON to builtin filetype and use Scintilla JSON lexer for it (PR #3647)

> > I didn't read the specs of JSON-LD but are those always present in the keys > > of json dicts? > > I suppose its the old lexers lack of context issue, IIUC the compact IRIs > need to be specified by `@context` specifications, otherwise they are just > strings with `:` in them. >From what I

[Github-comments] Re: [geany/geany] Add Prolog filetype support (PR #3171)

@techee > would you have a look at it if it looks alright? It's everything I would want, thanks! But where are the symbols? Or is tag parsing still on the TODO list? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3171#issuecomment-1776072916 You are

[Github-comments] Re: [geany/geany] Convert JSON to builtin filetype and use Scintilla JSON lexer for it (PR #3647)

@rdipardo commented on this pull request. > @@ -0,0 +1,59 @@ +# For complete documentation of this file, please see Geany's main documentation +[styling] +# Edit these in the colorscheme .conf file instead +default=default +number=number_1 +string=string_1 +stringeol=string_eol +propertyname=at

[Github-comments] [geany/geany] `AddGeanyLexers()` omits the AsciiDoc module since 19336d2 (Issue #3615)

19336d2 effectively removed AsciiDoc support by [deleting the reference to the lexer module][0]: https://github.com/geany/geany/blob/4246298dd8b3c70528cdad0554000f5d54f39765/scintilla/lexilla/src/Lexilla.cxx#L170-L177 The upshot is that `sci_set_lexer()` now gets a null pointer from `LexerNameF

[Github-comments] [geany/geany] Enable EOL-filled Markdown headings (PR #3602)

Before  After *with `lexer.markdown.header.eolfill=1`* 

[Github-comments] Re: [geany/geany] Do not enable Scintilla's Change History by default (PR #3591)

> Maybe Scintilla needs to export some controls, such as resetting when the > user does reload, although of course that can be undone, so maybe not. Some downstream projects have actually resorted to emptying the undo buffer on file reload, then toggling Scintilla's edit tracker off and on, to s

[Github-comments] Re: [geany/geany] Markdown syntax highlighting confused by empty image title (#2798)

@eht16, @elextr This issue can be closed as fixed in the forthcoming Geany.  -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2798#is

[Github-comments] Re: [geany/geany] Update Scintilla to version 5.3.6 (PR #3551)

Speaking of filedefs, has anyone had a chance to look at the suite of new properties the shell lexer acquired in recent versions? Most of them are for embedded variables, for example [inside here docs][1]: https://github.com/geany/geany/assets/59004801/045a6d60-ba67-4875-9948-c1d62ddfeac7"; />

[Github-comments] Re: [geany/geany] Update Scintilla to version 5.3.6 (PR #3551)

@elextr, yes, I see now the commit only touched filedefs (after expanding the diffs that GitHub's device fingerprinting scripts decided to collapse for my diminutive screen). At least the Prolog enthusiasts now have a mentioned thread to follow, in case they want to know what's blocking #3171.

[Github-comments] Re: [geany/geany] Update Scintilla to version 5.3.6 (PR #3551)

> [Handle new styles for strings in R (rawstrings, backticks, > espaces](https://github.com/geany/geany/pull/3551/commits/37b15b0cf9739c04ff50f53944e2874b095e52b6) I would defer to [@zufuliu's patch][0] as being simpler and slightly optimizing the iteration count. IIUC, [it's Geany's policy][1]

[Github-comments] Re: [geany/geany] Update lexilla to 5.2.4 (PR #3441)

@kugel- > this seems to be an artifact of an earlier lexilla update. I checked and in fact the GDScript filedef was never quite correct. It was copied almost verbatim from the Python filedef without a significant change since being added in f59e520. A point-in-time build based on f59e520 is mis

[Github-comments] Re: [geany/geany-plugins] Problem with Chinese display (Issue #1262)

> The red is output from the Java compiler, but it looks like it is not UTF-8 > encoding. @DarkgreenWorld set "JAVA_TOOL_OPTIONS=-Dfile.encoding=UTF8" or, https://github.com/geany/geany-plugins/assets/59004801/3327a097-c781-4b54-ad5d-4f3356be268a";> -- Reply to this email directly o

[Github-comments] Re: [geany/geany-plugins] Compiling geangy-plugins appeared errors (Issue #1255)

> @rdipardo probably not, the problems are in linking, not in compiling. Headers can provide `extern` declarations, which compile but still confound the linker, e.g. ~~~c /* * undef.h */ extern int foo(void); ~~~ ~~~c /* * undef.c */ #include "undef.h" int main(void) { return foo(); } ~~

[Github-comments] Re: [geany/geany-plugins] Compiling geangy-plugins appeared errors (Issue #1255)

> BTW have no idea why it works on Linux and what MSYS2 may have changed to > break it. If they bumped GCC [to 13.x], the refactored standard headers might've done it: [to 13.x]: https://gist.github.com/eht16/5b5ca97557c667a7a97e511b05677b8c#file-m

[Github-comments] Re: [geany/geany] Update lexilla to 5.2.4 (PR #3441)

GDScript's new annotation style has not been fully integrated yet. The [file type definition] still contains a `decorator=decorator` mapping. As a result, annotations don't show in [GDScript files] (lines 49, 51): ![gdscript-lexilla-524-no-annotations](https://github.com/geany/geany/assets/59004

[Github-comments] Re: [geany/geany] display problem with mono font: alphabet and chinese (Issue #3111)

> Maybe I'll take a shot at it after next scintilla release if I have time. There's already an isolated Lexilla upgrade proposed in #3441 A companion update for Scintilla should probably stick to the matching version, [5.3.4] in this case. (*The release notes mention Lexilla 5.2.__3__, but that

[Github-comments] Re: [geany/geany] display problem with mono font: alphabet and chinese (Issue #3111)

> there was a PR to do so #3292, but the contributor **deleted** it A PR's changes can always be recovered by visiting the "patch" URL, whether or not the branch still exists. Go to the PR on GitHub and add `.patch` to the address path, or go straight to the actual resource at

[Github-comments] Re: [geany/geany] Add Prolog filetype support (PR #3171)

The upstream Prlog lexer may be undergoing [a substantial refactoring](https://github.com/ScintillaOrg/lexilla/pull/178) soon. I can't seem to get Geany to build for me these days, but maybe now's a good time for @techee to synchronize his topic branch? -- Reply to this email directly or vie