[Github-comments] Re: [geany/geany-plugins] Debugger: Fix debugging of multi-threaded programs (PR #1170)
@nomadbyte I guess its waiting for "somebody" to review and test, IIRC @avafinger applied changes manually, it would be nice for someone to test the PR explicitly. LGB(very cursory)I -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1170#issuecomment-1463234672 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Debugger: Fix debugging of multi-threaded programs (PR #1170)
@nomadbyte pushed 1 commit. aa40d7cc1d6b415a7fd4bde4593193beb31f3e79 Debugger: Fix debugging of multi-threaded programs -- View it on GitHub: https://github.com/geany/geany-plugins/pull/1170/files/0abd437f60141bd63a1b5dc1aab9b042e5ae3f3e..aa40d7cc1d6b415a7fd4bde4593193beb31f3e79 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] The editor inserts a quote too much (Issue #3426)
You probably have _both_ Geany autoclose and the Autoclose plugin set to autoclose. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3426#issuecomment-1463039364 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] The editor inserts a quote too much (Issue #3426)
`Edit->Preferences->Editor->Completions->Autoclose quotes and brackets` untick as uppropriate. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3426#issuecomment-1463037523 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Improve code commenting-out global config files (PR #3413)
> So yeah, there surely is room for improvement, but I don't think going whole > "no non-overriden settings can ever be mentioned in filetype definitions" is > the best move. Yeah, that provides no guidance to users. > I think those are the ones showing up in filetypes definitions. E.g. > comment_use_indent: it's both a user preference, but also not all languages > are happy about it, or their canonical style isn't. Similarly, wordchars has > some use per-filetype, where identifiers are not limited to the usual (say, > they contain - for example). Which kind of argues against my suggestion above of having all of `filetypes.common` in each filetype file commented out. (the "usual" is rapidly becoming Unicode, eg C++ can now start with [XID_Start](https://www.unicode.org/reports/tr31/#Table_Lexical_Classes_for_Identifiers) and continue with zero or more [XID_Continue](https://www.unicode.org/reports/tr31/#Table_Lexical_Classes_for_Identifiers) and C is planned for version after C++23 IIRC, but thats another issue [@elextr clambers down off his "not all languages are C" soapbox] ) So ultimately I agree with @b4n that the simplest solution (add `#` to any line not starting with `[`) is best. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3413#issuecomment-1463031048 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Recognize .F77 extension (uppercase) as FORTRAN77 (PR #3427)
WFM -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3427#issuecomment-1462998822 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Add mingw-w64 (Windows) CI build (PR #1201)
@eht16 pushed 1 commit. 306f84c4f882e873f1aa68681cc41a3edb9416f0 CI: Add Windows build -- View it on GitHub: https://github.com/geany/geany-plugins/pull/1201/files/0d36c1d2d37cb909bdf118e538cbdfa28fe5f2cb..306f84c4f882e873f1aa68681cc41a3edb9416f0 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Add mingw-w64 (Windows) CI build (PR #1201)
@eht16 pushed 1 commit. 2c7bc518b1866be55d6cf9cd489d6e7f97d93379 Merge branch 'master' into ci_add_windows_build -- View it on GitHub: https://github.com/geany/geany-plugins/pull/1201/files/655eeaca7daae67a912c7093fc7fcd28b847c883..2c7bc518b1866be55d6cf9cd489d6e7f97d93379 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Improve code commenting-out global config files (PR #3413)
[read the thread] IMO, just use one single `#` as you did at the start, and don't worry about the `comment_use_indent` comment ~~comment comment~~ (oops, got carried away :upside_down_face:). * `# ` as documentation comments in conffiles is most common * `#key=value` as commented-out default/suggestion is common (many things in e.g. /etc do this) * `## ` is a *lot* less common, so is `#~ ` indeed. The one thing you possibly could do is still add a leading `#` to the `\t#comment` line, e.g. "if line is an indented comment, add a documentation comment prefix", but that might be an overly specific case to warrant it, and special cases have a tendency to come back to bite you… > and language-specific config files would contain only those values they > override to some other value than `filetypes.common` Hum, I'm not sure it's a great idea. Some settings make sense to be modified per-filetype rather than necessarily globally, and I think those are the ones showing up in filetypes definitions. E.g. `comment_use_indent`: it's both a user preference, but also not all languages are happy about it, or their canonical style isn't. Similarly, `wordchars` has some use per-filetype, where identifiers are not limited to the usual (say, they contain `-` for example). So yeah, there surely is room for improvement, but I don't think going whole "no non-overriden settings can ever be mentioned in filetype definitions" is the best move. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3413#issuecomment-1462908747 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Improve code commenting-out global config files (PR #3413)
(FWIW, I didn't read everything yet nor looked at the implementation, but I like the idea and it probably would have saved the author of #3425 some trouble) -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3413#issuecomment-1462884540 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] .F77 file extension does not syntax highlight (Issue #3425)
OK, so, I still cannot reproduce the issue (yet I have a clue, see below), but I made #3427 to fix that for good and make it "functional by default". Now, to what I think the issue is: looking at your screenshot of the *filetype_extensions.conf* file:  we don't really see clearly the symbols tree, but the piece we see `7 [30]` refers to the `F77` key: the line matches, and it should show up. However, it *seems* to be on the *second row of the tree*, which it should not. The tree should look like so:  Notice that: * `F77` is on the 3rd row * `Extensions [4]` above is wider so should show up in your capture. This leads me to believe that the issue is that you did not uncomment the `[Extensions]` section on line 4. Admittedly it's not obvious one has to do that, although [@elextr mentioned it](https://github.com/geany/geany/issues/3425#issuecomment-145877), but #3413 should improve the situation (and I believe, would have prevented you from most of the pain). FWIW, this *filetype_extensions.conf* should suffice to solve the initial issue: ```ini # Filetype extension configuration file for Geany # Insert as many items as you want, separate them with a ";". # See Geany's main documentation for details. [Extensions] F77=*.f;*.for;*.ftn;*.f77;*.F;*.FOR;*.FTN;*.fpp;*.FPP;*.F77; ``` -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3425#issuecomment-1462878977 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] [geany/geany] Recognize .F77 extension (uppercase) as FORTRAN77 (PR #3427)
Fixes #3425. You can view, comment on, or merge this pull request online at: https://github.com/geany/geany/pull/3427 -- Commit Summary -- * Recognize .F77 extension (uppercase) as FORTRAN77 -- File Changes -- M data/filetype_extensions.conf (2) -- Patch Links -- https://github.com/geany/geany/pull/3427.patch https://github.com/geany/geany/pull/3427.diff -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3427 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] Markdown: Modify replace_all to avoid infinite loop (PR #1232)
@b4n commented on this pull request. Not tested, but it looks good from here. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1232#pullrequestreview-1333809789 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)
@b4n commented on this pull request.
> +static gchar char_at(ScintillaObject *sci, gint pos)
+/*
+
+-
*/
+{
+return sci_get_char_at(sci, pos);
+}
Just curious: why the wrapper?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1221#pullrequestreview-1333787397
You are receiving this because you are subscribed to this thread.
Message ID:
[Github-comments] Re: [geany/geany-plugins] Remove unusable plugins: DevHelp, GeanyPy, Multiterm (PR #1217)
@eht16 Fine with me, I now merged the webhelper part, so at least I got the ball moving again (and I think it's in a fair enough state anyway). BTW I just gave a quick look at multiterm, and it's less trivial than I expected, so it'd require somebody actually motivated to do it. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1217#issuecomment-1462714188 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany-plugins] webhelper: Port to webkit2gtk (PR #1224)
Merged #1224 into master. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1224#event-8712112548 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] [geany/geany] The editor inserts a quote too much (Issue #3426)
Hi
I am learning C with Geany. When I write a function call like:
puts("
then Geany inserts a quote too much so that there are three:
printf(""");
The brackets are ok.
I am using Geany 1.38 on Linux mint.
Thank you for this nice editor
Sandor
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3426
You are receiving this because you are subscribed to this thread.
Message ID:
[Github-comments] Re: [geany/geany] Idea: Submenus for the "New" Menu (Issue #3357)
Now merged. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3357#issuecomment-1462359343 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Idea: Submenus for the "New" Menu (Issue #3357)
Closed #3357 as completed via #3397. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3357#event-8710041112 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Add filetype submenus for new file with template menus (PR #3397)
Merged #3397 into master. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3397#event-8710040796 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Idea: Submenus for the "New" Menu (Issue #3357)
@ntrel , awesome. Thanks! How soon until this is merged? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3357#issuecomment-1462328189 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] .F77 file extension does not syntax highlight (Issue #3425)
Note I also tested with LMDE 5 and the Geany it supplies, 1.37.1 as well as current git version, both worked. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3425#issuecomment-1462078069 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] .F77 file extension does not syntax highlight (Issue #3425)
Although you have reported it, if we can't reproduce it we can't fix it. Seems there is something unusual about your system that doesn't occur here. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3425#issuecomment-1462048319 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] .F77 file extension does not syntax highlight (Issue #3425)
As I said, works for me. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3425#issuecomment-1462039353 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] .F77 file extension does not syntax highlight (Issue #3425)
> > Geany stores whatever syntax it was using and never checks again […]. > > Stopping and starting Geany will not "fix" an existing opened file. > Isn't that the only real issue here? No. I had many files to choose from. I closed all that were open. I bounced Geany and chose different .F77 files. I just replicated the entire problem on this system as well.  I made the change to extensions, saved the file, bounced Geany, loaded a completely different .F77 file and had it not highlight. When *.F77; isn't dead last in the list, it works. When it is dead last highlighting does not work. At this point I'm done. I've reported the bug, reproduced the bug on an entirely different system, and answered questions. I use pictures so I don't get pulled into a terminology war and now I'm being pulled into a terminology war. I always paste everything in the report because using something like Gist is _exactly_ how critical information gets lost. Internet rot strikes without warning. Thank you for your time. I now have to go un-install Geany from the 6-8 machines that will be used for this project. They will either have to use Emacs to have a combined editor and GDB front end or split editor and GDB front end. Fix it, don't fix it, I've reported it and replicated it on different OS. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3425#issuecomment-1462032042 You are receiving this because you are subscribed to this thread. Message ID:
[Github-comments] Re: [geany/geany] Imprecise/Excessive scrolling in editor using touchpad (Issue #3319)
i guess this happens in the viewerport of gimp v2.10.2x / v2.10.3x too which also uses gtk. so upstream bug ig -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3319#issuecomment-1461545161 You are receiving this because you are subscribed to this thread. Message ID:
