[Github-comments] Re: [geany/geany] How it is implemented disabling GIO unsafe file saving in Geany? (Discussion #3697)

2023-11-20 Thread elextr via Github-comments
To emphasise @b4n's fourth bullet point, only the directory entries are changed, this probably only means modifying the inode number in the directory file and marking the old one free. And more on the footnote, not just SSDs, but with journalling file systems its guaranteed it won't be the same

[Github-comments] Re: [geany/geany] How it is implemented disabling GIO unsafe file saving in Geany? (Discussion #3697)

2023-11-20 Thread elextr via Github-comments
And don't forget shingled disks never overwrite, and have to move stuff around internally to defragment whole zones before reusing them. Also the miniscule costs of one extra directory write has to be balanced against the cost of running the computer for the time required to reproduce lost data

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

2023-11-20 Thread elextr via Github-comments
Couldn't be bothered with inertia. ;-) -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3694#issuecomment-1819991075 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] [RFC] API for LSP plugins (PR #3571)

2023-11-21 Thread elextr via Github-comments
> Mutex type prefixed with (*Mutex) while with our TMTags we'd have this in > scope Well, bearing in mind the limitations of my Go, I think what it is telling you is that the Mutex needs to be accessed via pointer, all users of a Mutex must access the same memory, they can't be separate instanc

[Github-comments] Re: [geany/geany] [RFC] API for LSP plugins (PR #3571)

2023-11-21 Thread elextr via Github-comments
> I'm a go user myself and I know what that means Sorry, I thought you just owned a plush gopher, not that you were a gopher, have to watch out you don't start Goany. So leaving testing gopls to you. :grin: Ahem, anyway back to LSPs. Basically we seem to be in vociferous agreement, but from dif

[Github-comments] Re: [geany/geany-plugins] Fix handling of locals (PR #1294)

2023-11-21 Thread elextr via Github-comments
LGBI. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1294#issuecomment-1821910533 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany-plugins] Various small WebHelper improvements (PR #1295)

2023-11-21 Thread elextr via Github-comments
Documentation looks ok, rest went zooming over my head. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/pull/1295#issuecomment-1821933103 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] How it is implemented disabling GIO unsafe file saving in Geany? (Discussion #3697)

2023-11-22 Thread elextr via Github-comments
> The probability of a "disaster" of this type (during that very short saving > time) is so infinitesimally small that does not justify these methods. You may hold that personal opinion, fine, but many others, including most of those who make and use Geany and those who make GIO do not agree. A

[Github-comments] Re: [geany/geany] Add `.mjs` extension for JavaScript (PR #3698)

2023-11-22 Thread elextr via Github-comments
Looks ok to me. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3698#issuecomment-1822676169 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Auto-scroll to first error in Compiler tab on failed builds (Issue #3699)

2023-11-22 Thread elextr via Github-comments
The user needs to see the end message to tell if it succeeded (eg all warnings, no errors), that would not be visible if the compile output window scrolled to the top when complete. But `next error` after the build is finished goes to the first error/warning so the user is able to read the buil

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

2023-11-22 Thread elextr via Github-comments
Merged #3694 into master. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3694#event-11044191091 You are receiving this because you are subscribed to this thread. Message ID:

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

2023-11-22 Thread elextr via Github-comments
Thanks, although I don't have pascal to test it, since nobody objected, so I overcame the inertia and merged ;-) -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3694#issuecomment-1823940880 You are receiving this because you are subscribed to this thread

[Github-comments] Re: [geany/geany] File contents after NUL character are not read or rendered (Issue #3700)

2023-11-23 Thread elextr via Github-comments
Closed #3700 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3700#event-11047880530 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] File contents after NUL character are not read or rendered (Issue #3700)

2023-11-23 Thread elextr via Github-comments
Closing as duplicate of #3686 and many more right back to #618 -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3700#issuecomment-1824459127 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] File contents after NUL character are not read or rendered (Issue #3700)

2023-11-23 Thread elextr via Github-comments
> @elextr not supporting NULs is one thing, but we should not truncate silently > (and we think we don't do that, so if we do there's a problem somewhere). Agreed, but the OP doesn't mention that, like I said elsewhere the code has evolved to be a bit of a mess and I wouldn't be surprised if it

[Github-comments] Re: [geany/geany] Allow to disable: Are you sure to replace in the whole session? (Issue #3702)

2023-11-23 Thread elextr via Github-comments
The "In Session" function is not new, all that is new is the warning message, added [here](https://github.com/geany/geany/commit/295f59da91d2a2c08a5289d56d30f3caa2d2d507). The "In Session" replace although it has been available for at least 15 years (as far as I looked). There is no option to

[Github-comments] Re: [geany/geany] Allow to disable: Are you sure to replace in the whole session? (Issue #3702)

2023-11-23 Thread elextr via Github-comments
Closed #3702 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3702#event-11051849119 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] changed file extension: build commands did not change (Issue #3525)

2023-11-23 Thread elextr via Github-comments
Closed #3525 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3525#event-11051884082 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Blurred text (Issue #3701)

2023-11-23 Thread elextr via Github-comments
See https://github.com/geany/geany/issues/3610 Basic advice, try other fonts. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3701#issuecomment-1825051020 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] replace xterm with gnome-terminal (Issue #3703)

2023-11-23 Thread elextr via Github-comments
> but the RUN botton can not display as an "STOP" icon, that's say I can not > stop the running application by click the RUN button. IIUC `gnome-terminal` is a front end for `gnome-terminal-server`. The server shows the terminal screens and `gnome-terminal` just tells it what to show and exits

[Github-comments] Re: [geany/geany] File contents after NUL character are not read or rendered (Issue #3700)

2023-11-23 Thread elextr via Github-comments
@dolik-rce > It almost feels like it depends on how things happen to be layed out in > memory or something else undefined behaviorish. Laid out in the file more specifically, Geany tries to be "helpful", unless the user specifies an encoding, Geany will try all the ones it knows about to see

[Github-comments] Re: [geany/geany] Allow to disable: Are you sure to replace in the whole session? (Issue #3702)

2023-11-24 Thread elextr via Github-comments
> @elextr are you sure you didn't understand the request upside down? I > understand as the OP asking to disable the warning and get back the older > behavior of not asking confirmation. Good question, could be either, but hey, "somebody" can follow the usual Geany approach of adding another op

[Github-comments] Re: [geany/geany] replace xterm with gnome-terminal (Issue #3703)

2023-11-24 Thread elextr via Github-comments
[This](https://manpages.ubuntu.com/manpages/jammy/en/man1/gnome-terminal.1.html) was what google found for me, maybe a newer version has that option. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3703#issuecomment-1825542036 You are receiving this be

[Github-comments] Re: [geany/geany] File contents after NUL character are not read or rendered (Issue #3700)

2023-11-24 Thread elextr via Github-comments
@jmfernandez (and all the others asking the same thing) it doesn't matter how many use-cases are presented, "somebody" has to NUL safe all of Geany code, and all plugins, and only then will it be a responsible thing to load files containing NULs, simply loading files is easy, checking and correc

[Github-comments] Re: [geany/geany] replace xterm with gnome-terminal (Issue #3703)

2023-11-24 Thread elextr via Github-comments
Works for me `gnome-terminal -e python3` returns immediately and a window with python REPL pops up, but `gnome-terminal --wait -e python3` does not return until after the Python REPL is exited. Note `-e` is also deprecated, @eexpress use `--` and look at how the arguments need to be structured.

[Github-comments] Re: [geany/geany] [Feature request] Add an item in the file tab's context menu to open the file's containing folder (Issue #3704)

2023-11-24 Thread elextr via Github-comments
Open the directory where? Or do you mean open the `Open File` dialog with the directory set to that of the file, and the file itself chosen? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3704#issuecomment-1826166110 You are receiving this because

[Github-comments] Re: [geany/geany] [Feature request] Add an item in the file tab's context menu to open the file's containing folder (Issue #3704)

2023-11-25 Thread elextr via Github-comments
Or in file browser plugin? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3704#issuecomment-1826267169 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] replace xterm with gnome-terminal (Issue #3703)

2023-11-25 Thread elextr via Github-comments
Closed #3703 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3703#event-11060419446 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] File contents after NUL character are not read or rendered (Issue #3700)

2023-11-25 Thread elextr via Github-comments
> I'll try and have a stab at cleaning it up a tiny bit and avoid the loading > of partial files without notifying. Good luck, have a supply of wet forehead cloths ready. Totally agree the warning should be more visible, a nice fat infobar would be good, they didn't exist when Geany was written

[Github-comments] Re: [geany/geany] How to move line item Terminal to top and always open this at launch of Geany? (Discussion #3705)

2023-11-25 Thread elextr via Github-comments
There is no existing way to move the terminal to the top, and I'm not sure what that will gain, but it may break code that assumes status is first. Also note the terminal is not available on Windows and is optional on Linux. If "somebody" made a well written PR to save and restore the current m

[Github-comments] Re: [geany/geany] Blurred text (Issue #3701)

2023-11-27 Thread elextr via Github-comments
Well, you actually only tried Lato and DejaVu fonts, monospace is an alias, usually of DejaVu. DejaVu is rubbish, I do wish distros wouldn't set it as default, but on my system here I can't see any difference between Geany 1.38 and 2.0 with DejaVu sans mono, and neither looks "blurry" until the

[Github-comments] Re: [geany/geany] [Feature request] Add an item in the file tab's context menu to open the file's containing folder (Issue #3704)

2023-11-27 Thread elextr via Github-comments
Well, "somebody" can make a pull request adding a menu item that is called "Open in file manager". Because there are so many file managers this will also need a setting that specifies the command to run and which interpolates the path, for example at %f. If the distro does not set that to the

[Github-comments] Re: [geany/geany] Geany 2.0 toggle All Additional Widgets spawns empty status bar (Issue #3706)

2023-11-28 Thread elextr via Github-comments
What OS? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3706#issuecomment-1829468596 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Geany 2.0 toggle All Additional Widgets spawns empty status bar (Issue #3706)

2023-11-28 Thread elextr via Github-comments
Toggle additional widgets applies to three things, the message window, the toolbar and the status bar. The first two have menu checkboxes to control them and the toggle sets those menu items to the relevant state so the settings match whats visible. Eg turn the toolbar checkbox off and the t

[Github-comments] Re: [geany/geany-plugins] Error: Most Plugins not binary compatible with this release of geany. Therefore not available in Plugin Manager Dialog (Issue #1292)

2023-11-30 Thread elextr via Github-comments
Is the right version of libgit2 available? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1292#issuecomment-1833667456 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Add "session-opening" signal emitted when session opening starts/stops (PR #3707)

2023-11-30 Thread elextr via Github-comments
Does this fix #3684? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3707#issuecomment-1835126585 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] required gtk+ version 3.20, current version is 2.24 (Issue #3708)

2023-12-01 Thread elextr via Github-comments
what is the output of `geany --version` ? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3708#issuecomment-1836892264 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Geany opens but if it has arguments it doesn't (Issue #3709)

2023-12-01 Thread elextr via Github-comments
Geany thinks there is another instance already running and it tells that instance to open the file then exits. Try deleting the file `/root/.config/geany/geany_socket_puppypc19012__0`. Also I have to make the usual caveat, it appears you may be runing Geany as root. Geany is not made to be run

[Github-comments] Re: [geany/geany] Add `.mjs` extension for JavaScript (PR #3698)

2023-12-02 Thread elextr via Github-comments
Nobody is full time on this project, its always polite to leave some time for objections. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3698#issuecomment-1837281115 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] geany ver2.0 still indentation problem: tab and space (Issue #3710)

2023-12-03 Thread elextr via Github-comments
Hint, monospaced, the width of tabs shown is the width of the specified number of ASCII space characters in the current default font. With non-monospaced fonts that may be less than the width of the same number of other characters, and that width may depend on the number of spaces in a row.

[Github-comments] Re: [geany/geany] Add `.mjs` extension for JavaScript (PR #3698)

2023-12-04 Thread elextr via Github-comments
@creatxrgithub that is not relevant to this PR, please do not hijack existing issues or pull requests, create your own. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3698#issuecomment-1838188623 You are receiving this because you are subscribed to this

[Github-comments] Re: [geany/geany] Error trying to compile Kotlin w/ kotlinc..... (Issue #3138)

2023-12-04 Thread elextr via Github-comments
@jmpessoa its already closed, that does not prevent anyone accessing it, and you were even able to post to it. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3138#issuecomment-1839957451 You are receiving this because you are subscribed to this thread

[Github-comments] Re: [geany/geany] Enumerated value of file_disk_status immediately reset to FILE_OK (Issue #3711)

2023-12-05 Thread elextr via Github-comments
The `FILE_CHANGED` value is only used by the GIO file monitoring code AFAICT. That is never enabled because it has issues with multiple triggering (possibly due to the documented erorrs and incompletnes of inotify(7)) but its left there in case "somebody" figures it out and fixes it. If not at

[Github-comments] Re: [geany/geany] Enumerated value of file_disk_status immediately reset to FILE_OK (Issue #3711)

2023-12-06 Thread elextr via Github-comments
Remember I said "possibly", GIO may also use plain polling just like Geany does, also not helping its determinism ;-). And even if it uses `inotify` Geany has no way to control the flags GIO uses. And of course it must use something else on Windows, not sure about Macos. These portability is

[Github-comments] Re: [geany/geany] A question about `lexer_filetype` (Discussion #3713)

2023-12-06 Thread elextr via Github-comments
There is no csharp lexer, it uses the C lexer [here](https://github.com/geany/geany/blob/e5680fe85de536fc61ff0f2d4eadc54171d6c982/data/filedefs/filetypes.cs#L15). So it should be `C`. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3713#discus

[Github-comments] Re: [geany/geany] A question about `lexer_filetype` (Discussion #3713)

2023-12-06 Thread elextr via Github-comments
Look at the `filetypes.xxx` file, if it has no `lexer_filetype` setting but the language has highlighting then it has its own lexer and can be a value for a custom filetype's `lexer_filetype` setting, so `Ada`. There are no properties set in `filetypes.ada` for Ada, but it would be best for you

[Github-comments] Re: [geany/geany] A question about `lexer_filetype` (Discussion #3713)

2023-12-07 Thread elextr via Github-comments
To be clear, there are two categories of filetypes, built-in and custom. Lexers and ctags parsers are pieces of code obtained from external projects that are compiled into Geany. Built-in filetypes (like C and Ada) are defined in the Geany code so they can point to the lexer and parser code the

[Github-comments] Re: [geany/geany] Make Geany 2.0 available on Raspberry Pi (5) (Discussion #3715)

2023-12-07 Thread elextr via Github-comments
The Geany project does not make packages for any Linux distros so that is a question for whoever packages Geany for RPi. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3715#discussioncomment-7794443 You are receiving this because you are subscrib

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-08 Thread elextr via Github-comments
LGBI, I didn't inspect the test code more than a (very) quick skim. Compiles ok, but encoding tests not made because not in `tests/meson.build` and being an ASCII locale I have no other encodings, so untested. The whole encodings thing is still a mess, but its now looks a more correct mess :

[Github-comments] Re: [geany/geany] Enumerated value of file_disk_status immediately reset to FILE_OK (Issue #3711)

2023-12-09 Thread elextr via Github-comments
As you said [here](https://github.com/geany/geany/issues/2540#issuecomment-1774779482), you want to make two lists: Just to be clear about something, the _document_ is the in memory object, the _file_ is the thing on disk. For open documents where the file has changed on disk, you want a list

[Github-comments] Re: [geany/geany-plugins] projectorganizer: prjorg-sidebar.c: Cast g_ptr_array_free to gchar** (PR #1298)

2023-12-09 Thread elextr via Github-comments
Sigh C!!! [exasperated tone] Surely it can trace the type of the pointers that were put in the array as `gchar*` where they were implicitly converted to `void*` and so allow the therefore legal implicit conversion from `void*` to `gchar*` in the return :stuck_out_tongue_winking_eye: Anyway LG

[Github-comments] Re: [geany/geany] Correction of issue #3678 (PR #3681)

2023-12-09 Thread elextr via Github-comments
> If you'd like to focus the search field instead (which indeed might make > sense, but I don't have a strong opinion yet) Nah, I use the moose, so I can click on what I want. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3681#issuecomment-1848829828

[Github-comments] Re: [geany/geany-plugins] projectorganizer: prjorg-sidebar.c: Cast g_ptr_array_free to gchar** (PR #1298)

2023-12-09 Thread elextr via Github-comments
The `` thing (which is C++ not C) is within the C++ standard that allows any header to include any other header (or not, which is what they changed, some headers that used to use it no longer do). Users should always include what they use irrespective of "automagic" inclusions in headers since

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-10 Thread elextr via Github-comments
> that joy of having multiple build systems to maintain is back Feel free to remove autotools :wink: Anyway, tests seem to pass, although with 10 billion[^1] `Geany-INFO` messages. Several of these messages appear: ``` # Geany-INFO: Couldn't convert from ISO-8859-8-I to UTF-8 (Conversion from

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-10 Thread elextr via Github-comments
> Anyhow, yes, this could be improved, and ideally we'd probably not display > the encoding in the list if it's not supported by the library we use (iconv), > as it makes little sense then. Would be nice but IIRC last time we discussed this there was no easy way of finding what was supported by

[Github-comments] Re: [geany/geany] non-deterministic anon_struct (Issue #3717)

2023-12-11 Thread elextr via Github-comments
This generated name is created by the ctags CXX parser [here](https://github.com/geany/geany/blob/512e88df8d97284c191459450bce4dd7877b9c2b/ctags/main/parse.c#L4795). The value of `parser -> anonymousIdentiferId` is incremented a few lines above, so I suspect its intended to count anon structs an

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-11 Thread elextr via Github-comments
> It's (almost, but is for all practical purposes) documented as using > g_iconv(), which is documented as using iconv() or libiconv as fallback. Ok, the [code-ocumentation](https://github.com/GNOME/glib/blob/main/glib/gconvert.c) shows its iconv all the way, not a #ifdef windows in sight :-)

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-12 Thread elextr via Github-comments
> including propagating the error better as you wished, as well as not showing > knowingly unsupported encodings in the UI In the end thats all I am suggesting adding now. > removing a unnecessary control in the preferences regarding file encodings. Which one? I only found encoding of new fil

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-12 Thread elextr via Github-comments
> or should we keep the "fix encodings conversion" separate from the more > cosmetic stuff? Well, ATM its just tests and fixes AFAICT, not sure what you see as "cosmetic"? PS sure its several fixes, but they are all just part of making encoding work correctly, or as correctly as it can be made

[Github-comments] Re: [geany/geany] Remove deprecated Doxygen settings (PR #3719)

2023-12-12 Thread elextr via Github-comments
Is the complaint new to a new versio0n of doxygen? And if we change it will it break old versions? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3719#issuecomment-1852938359 You are receiving this because you are subscribed to this thread. Message ID:

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

2023-12-12 Thread elextr via Github-comments
Do you mean "wrap" or "break" ? Wrap is a display only thing and happens only at the right edge of the screen. Break is actually modifying the text to include line breaks and happens at the long line setting. -- Reply to this email directly or view it on GitHub: https://github.com/geany/gean

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-12 Thread elextr via Github-comments
> Use fixed encoding when opening non-Unicode files. It's useful, but we have > code for adding a Detect from file entry directly in the combo box, as used > in the file Open dialog. Using this there as well instead of having a > separate checkbox strikes me as an improvement: simpler UI with le

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-12 Thread elextr via Github-comments
> I count the more proper error message as cosmetic compared to the other > fixes. And as you may have guessed I see them as fixes, so of course I say all in together :wink: Will check the strings as soon as I find my purple editing pencil. -- Reply to this email directly or view it on GitHu

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-12 Thread elextr via Github-comments
> @elextr it's already in the open dialog, and I'm not gonna move anything. I'm > just gonna merge Use fixed encoding when opening non-Unicode files checkbox > and Default encoding (existing non-Unicode files) combo, only keeping the > combo and having an additional Detect from file item in it w

[Github-comments] Re: [geany/geany] Various encodings conversion fixes (PR #3716)

2023-12-12 Thread elextr via Github-comments
> All this commenting is for the future PR with it, no point in discussing thin > air, it's confusing for no reason ;) Ok, waiting for separate concrete :smile: -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3716#issuecomment-1852998898 You are receivi

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

2023-12-12 Thread elextr via Github-comments
@rdipardo > Can the column boundary marker actually enforce the column limit, instead of > just visually indicating where a break should ideally occur? Is that not `Document->Line breaking`? I'm afraid your diagram was more confusing than helpful, the lines you have noted as "ok" are wrapped (

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

2023-12-12 Thread elextr via Github-comments
Note, line breaking does not break lines when typing adds characters before the column limit, even if that pushes characters on the line past the limit. Why? Its complicated, let me show why. In the following | means the breaking column and the successive snippets separated by blank lines are

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

2023-12-13 Thread elextr via Github-comments
@ineuw @rdipardo as I said above, is the functionality illustrated in the video not `Document->Line breaking` ?? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3718#discussioncomment-7848850 You are receiving this because you are subscribed to th

[Github-comments] Re: [geany/geany] geany build and run same time (#1327)

2023-12-15 Thread elextr via Github-comments
@pik33 as I said many times above `&&` is a _shell_ construct. Windows does not run commands in a Unix shell, so you cannot use `&&`. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1327#issuecomment-1858559384 You are receiving this because you are s

[Github-comments] Re: [geany/geany] Geany 2.0: indendation ignored (Issue #3721)

2023-12-15 Thread elextr via Github-comments
What is inserted for indentation is set in `Document->Indent Type->Spaces` and number by `Document->Indent Width->4` (or whatever). The values for those two settings are set on loading a file is to the value in preferences or project properties which overrides the preferences if a project is op

[Github-comments] Re: [geany/geany] Geany 2.0: indendation ignored (Issue #3721)

2023-12-16 Thread elextr via Github-comments
Closed #3721 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3721#event-11266848197 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] [Feature request] Zig Language Support (Issue #3724)

2023-12-18 Thread elextr via Github-comments
You could try making a custom filetype [(read the fine manual)](https://www.geany.org/manual/current/index.html#custom-filetypes) if one of the existing highlighters is "good enough" when given your keyword list (maybe C), and if a parser is good enough (probably not). Otherwise a parser needs

[Github-comments] Re: [geany/geany] error device (Issue #3726)

2023-12-19 Thread elextr via Github-comments
I suspect that the message is not from Geany, can you switch your machine to English and run Geany so we can see the original untranslated message to see if it comes from Geany? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3726#issuecomment-1862384

[Github-comments] Re: [geany/geany] error device (Issue #3726)

2023-12-19 Thread elextr via Github-comments
I'm sorry, without the machine and Geany being in English most contributors cannot tell what you were clicking on or what messages say. Possibly another contributor can read the messages and might help. Note that even if Geany shows the dialog, the messages may come from the system, or GTK, so

[Github-comments] Re: [geany/geany] error device (Issue #3726)

2023-12-19 Thread elextr via Github-comments
> when I click eject, but physical not eject, I see this error. When I physical eject, error no. But, CD I cannot physical eject I do not completely follow what you are saying, but if you click eject I suspect Windows decides the device is not available (unmounted in Linux parlance), even if it

[Github-comments] Re: [geany/geany] Remove deprecated Doxygen settings (PR #3719)

2023-12-19 Thread elextr via Github-comments
Did you diff the XML and the GRRR, sorry GIR? :smile: -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3719#issuecomment-1863551310 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Opening of very large JSON is extremely slow (Issue #3727)

2023-12-20 Thread elextr via Github-comments
Select filetype `None` on the open dialog. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3727#issuecomment-1865130118 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Opening of very large JSON is extremely slow (Issue #3727)

2023-12-20 Thread elextr via Github-comments
On the open dialog (ie _before_ opening) there is an expander lower left corner `More options` where there is a `Set filetype` combo. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3727#issuecomment-1865236978 You are receiving this because you are su

[Github-comments] Re: [geany/geany] Opening of very large JSON is extremely slow (Issue #3727)

2023-12-20 Thread elextr via Github-comments
Won't work, there is no way of setting filetype from the command line. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3727#issuecomment-1865242290 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Opening of very large JSON is extremely slow (Issue #3727)

2023-12-20 Thread elextr via Github-comments
"Somebody" could make a PR to add such a setting but given it would have to load _all_ files as filetype `none` it would remove a lot of Geany functionality. So its unlikely that it would be used much, and given there is a workaround opening from the Geany open dialog, I don't know if the PR wo

[Github-comments] Re: [geany/geany] Opening of very large JSON is extremely slow (Issue #3727)

2023-12-20 Thread elextr via Github-comments
Yes, that has the advantage that it only removes features from JSON filetypes, but the disadvantage of having to edit the config to turn it back on. Swings and roundabouts[^1] really, but its another workaround. [^1]: https://www.collinsdictionary.com/dictionary/english/swings-and-roundabouts

[Github-comments] Re: [geany/geany] Highlight C function names (patch available) (#1231)

2023-12-22 Thread elextr via Github-comments
A better way of doing this would be using a language server for which @techee has an implementation at [geany-lsp](https://github.com/techee/geany-lsp) that uses clangd (and pyls and gopls). The LSP protocol allows for semantic tokens for "functions" but its not enabled yet since it is not an

[Github-comments] Re: [geany/geany] Debian "sensible-browser" ignores the preferences of the x-www-browser file in Linux Mint. (Issue #3729)

2023-12-27 Thread elextr via Github-comments
Closed #3729 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3729#event-11348615272 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Debian "sensible-browser" ignores the preferences of the x-www-browser file in Linux Mint. (Issue #3729)

2023-12-27 Thread elextr via Github-comments
This isn't anything to do with Geany, maybe file elsewhere? -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3729#issuecomment-1870842785 You are receiving this because you are subscribed to this thread. Message ID:

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

2023-12-28 Thread elextr via Github-comments
The problem with GTK3 is that on Wayland it depends on the compositor, Mutter, a Gnome component. At some point Mutter will break/remove something GTK3 needs, ok it could maybe be synthesised in GTK3, but nobody at Gnome is going to want to be bothered, they have GTK4/5/6 ... -- Reply to this

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

2023-12-28 Thread elextr via Github-comments
Maybe we could wait for another complex UI application like Gimp to move to GTK4 and then copy all the widgets it re-implements, in fact they could be made into a toolkit library, the Gimp ToolKit maybe ... oh yeah right ok, GTK2 :smile: -- Reply to this email directly or view it on GitHub: h

[Github-comments] Re: [geany/geany] Limit the size of GUI icons (Issue #3730)

2023-12-28 Thread elextr via Github-comments
The size of icons is determined by the GTK toolkit, not Geany, you could see what GTK CSS can do. Since you didn't admit what you actually did to screw up your icons it might not be able to reduce the size. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/is

[Github-comments] Re: [geany/geany] Limit the size of GUI icons (Issue #3730)

2023-12-28 Thread elextr via Github-comments
I think you have told the system that 128x128 icons are "small" so GTK uses them when told to use "small" icons a. probably nothing can limit them, they are bitmap icons that can't be resized, no graphics toolkit has a whole bitmap image scaling tool (think Photoshop or Gimp) built in, only SVG

[Github-comments] Re: [geany/geany] Limit the size of GUI icons (Issue #3730)

2023-12-28 Thread elextr via Github-comments
Closed as not Geany -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3730#issuecomment-1871624702 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Limit the size of GUI icons (Issue #3730)

2023-12-28 Thread elextr via Github-comments
Closed #3730 as not planned. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3730#event-11354172469 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Limit the size of GUI icons (Issue #3730)

2023-12-28 Thread elextr via Github-comments
Nobody can see your system, or knows its arrangement, when asking questions like that you need to provide enough information to be able to understand it. "sda1" and "sda2" usually refer to the raw disk partitions on a Linux system, not a file. -- Reply to this email directly or view it on GitH

[Github-comments] Re: [geany/geany] Limit the size of GUI icons (Issue #3730)

2023-12-28 Thread elextr via Github-comments
First, please do not spam all those watching this repository with massive listings, file contents, or other large content, place those in a Gist and put a link in the post here. To emphasise, it is your GTK theme that specifies the icons on buttons, not Geany. My theme has no icons on "View",

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

2023-12-28 Thread elextr via Github-comments
As I'm not a javaist I don't know how Java decides the file encoding, but if its locale (GR, really BAD idea) maybe its different in Geany to in a terminal. This can happen if Geany is started from a system menu that does not run a shell to import your `.bashrc` `.profile` or wherever else

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

2023-12-28 Thread elextr via Github-comments
Transferred to mac repo, they can send back if its not specific. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3731#discussioncomment-7969710 You are receiving this because you are subscribed to this thread. Message ID:

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

2023-12-28 Thread elextr via Github-comments
Damn, can't seem to transfer, @techee maybe geany-osx needs to have discussions enabled or something -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3731#discussioncomment-7969715 You are receiving this because you are subscribed to this thread.

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

2023-12-28 Thread elextr via Github-comments
@Syntonica I just remembered (well I don't use Macs) that there is a special wrapper executable for OSX that reads stuff like locale and theme and so on from a `geany_mac.conf` file, maybe you had modified that and it was overwritten when the new version was installed? -- Reply to this email d

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

2023-12-29 Thread elextr via Github-comments
Well in your case its not Geany, its Java. My guess is java decides what the file encoding is from the environment it inherits from Geany when Geany runs the build command, which is the environment Geany inherited when it was started by the wrapper, which is what was set in the conf file. Th

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

2023-12-29 Thread elextr via Github-comments
@rdipardo thanks, @Syntonica could add that to the command in the makefile maybe. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/discussions/3731#discussioncomment-7971645 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] "Match m of N" in the status bar when searching (#2159)

2023-12-30 Thread elextr via Github-comments
Then contribute it, Geany is a totally volunteer project, and the fact that nobody has done anything since 2019 indicates that its either difficult to do, or do well, or nobody feels its more important to them than many other things they want to do. -- Reply to this email directly or view it o

[Github-comments] Re: [geany/geany] cannot build and install Geany 2.0 in chromeos (Issue #3732)

2023-12-30 Thread elextr via Github-comments
Probably intltools I think. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3732#issuecomment-1872591020 You are receiving this because you are subscribed to this thread. Message ID:

  1   2   3   4   5   6   7   8   9   10   >