[Github-comments] Re: [geany/geany] Safe implementation of Re-load All feature (PR #3722)

2024-04-17 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. 50218aea00d363a69674466693dfae1c7a86168c Merge branch 'geany:master' into re-load-all -- View it on GitHub: https://github.com/geany/geany/pull/3722/files/be0d5c69c0a9a92ebafc63f0154dd11dd8bf54a7..50218aea00d363a69674466693dfae1c7a86168c You are receiving

[Github-comments] Re: [geany/geany] Safe implementation of Re-load All feature (PR #3722)

2024-04-10 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. be0d5c69c0a9a92ebafc63f0154dd11dd8bf54a7 Merge branch 'geany:master' into re-load-all -- View it on GitHub: https://github.com/geany/geany/pull/3722/files/1a011193fb9694fd823736f2d7cca8c2125ee17e..be0d5c69c0a9a92ebafc63f0154dd11dd8bf54a7 You are receiving

[Github-comments] Re: [geany/geany] Safe implementation of Re-load All feature (PR #3722)

2024-04-07 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. 1a011193fb9694fd823736f2d7cca8c2125ee17e Merge branch 'geany:master' into re-load-all -- View it on GitHub: https://github.com/geany/geany/pull/3722/files/59dd6a99286f9a60508dfc6190ad760890cede6c..1a011193fb9694fd823736f2d7cca8c2125ee17e You are receiving

[Github-comments] Re: [geany/geany] Safe implementation of Re-load All feature (PR #3722)

2024-04-02 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. 59dd6a99286f9a60508dfc6190ad760890cede6c Merge branch 'geany:master' into re-load-all -- View it on GitHub: https://github.com/geany/geany/pull/3722/files/264507104da2bc35d3ce5db58c82fe88ecd8ecbe..59dd6a99286f9a60508dfc6190ad760890cede6c You are receiving

[Github-comments] Re: [geany/geany] Safe implementation of Re-load All feature (PR #3722)

2024-02-15 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. 09d1687554125cfdb19eb9dc9e09e3021a87ebef Merge branch 'geany:master' into re-load-all -- View it on GitHub: https://github.com/geany/geany/pull/3722/files/c73b5f46abb1c55e15d84cef6ca93e859d5d5d11..09d1687554125cfdb19eb9dc9e09e3021a87ebef You are receiving

[Github-comments] [geany/geany] Safe implementation of Re-load All feature (PR #3722)

2023-12-17 Thread Peter C. S. Scholtens via Github-comments
The Re-load All feature is implemented with a check if the files are modified inside the memory buffer. The buttons on the info_bar are drawn vertically, as there can be as much as five options, depending on the scenario, see picture below. See also the discussion

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

2023-12-14 Thread Peter C. S. Scholtens via Github-comments
As OP, this issue is outdated. See also [here](https://github.com/geany/geany/issues/2540). -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3711#issuecomment-1855590273 You are receiving this because you are subscribed to this thread. Message ID:

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

2023-12-14 Thread Peter C. S. Scholtens via Github-comments
Closed #3711 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3711#event-11246344602 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Reload all (#2540)

2023-12-14 Thread Peter C. S. Scholtens via Github-comments
I've elaborated a version which does allow re-loading all files which are **not-modified**, see the [branch here](https://github.com/peter-scholtens/geany/tree/re-load-all). The functionality is present under the pulldown menu _File -> Reload All (unmodified files only)_ of the main window.

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

2023-12-10 Thread Peter C. S. Scholtens via Github-comments
As end user I want to see all relevant data at once, as the typical use case is that either a revision control tool (or untar, unzip,...) is modifying a lot of files at ones. Therefore I created `document_check_disk_status_others(.., gboolean force)` which can be called when re-entering the

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

2023-12-09 Thread Peter C. S. Scholtens via Github-comments
The function `document_check_disk_status()` must be disentangled for a [Reload all](https://github.com/geany/geany/issues/2540) feature as first **all** file modifications have to be examined before **any** correct display warning can be created. Furthermore, I interpret the value of

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

2023-12-06 Thread Peter C. S. Scholtens via Github-comments
Reading the documentation on the man page, I assume that using the mask `IN_ONESHOT` may solve a problem that possibly arises: when a file is saved, it is actually modified again, which triggers another event. This recursion presumably happens even apart from all possible race conditions in

[Github-comments] [geany/geany] Boolean value of file_disk_status immediatly reset (Issue #3711)

2023-12-05 Thread Peter C. S. Scholtens via Github-comments
1. At [line 3747 of document.c](https://github.com/geany/geany/blob/e5680fe85de536fc61ff0f2d4eadc54171d6c982/src/document.c#L3747C31-L3747C31) the value of `doc->priv->file_disk_status` is set to `FILE_OK` **immediately after it was set to** `FILE_CHANGED`. This seems a bug, possible this

[Github-comments] Re: [geany/geany] Reload all (#2540)

2023-10-23 Thread Peter C. S. Scholtens via Github-comments
> If "somebody" contributed a PR that solved those issues in a reasonable > manner it could be accepted, but as a totally volunteer project there are no > "plans" other than what people contribute. I could try to write a pull request, but writing C instead of Rust feels like skydiving without

[Github-comments] Re: [geany/geany] "Join Lines" doesn't explain the sequence of how the lines are joined. (Issue #3590)

2023-10-23 Thread Peter C. S. Scholtens via Github-comments
Closed #3590 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3590#event-10737205800 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Reload all (#2540)

2023-10-23 Thread Peter C. S. Scholtens via Github-comments
As mentioned above, changing a branch in a revision control is a valid use case, running auto-formatting tools a.k.a. _code beautifiers_ like [`cargo fmt`](https://doc.rust-lang.org/book/appendix-04-useful-development-tools.html) and [pgFormatter](https://sqlformat.darold.net/) are too. I'm

[Github-comments] Re: [geany/geany] "Join Lines" doesn't explain the sequence of how the lines are joined. (Issue #3590)

2023-10-11 Thread Peter C. S. Scholtens via Github-comments
I was not familiar with this _join lines_ feature, so possible there is no better way to introduce users to it. About the the `_U`, I see no collision with other keys in "en_US" language mode. See the screenshot below (so instead of `Alt`+`E`+`F`+`N` we could choose `Alt`+`E`+`F`+`U`):

[Github-comments] Re: [geany/geany] Tooltip unclear: suggestion for better distinction between two options for backspace (Issue #3588)

2023-10-10 Thread Peter C. S. Scholtens via Github-comments
Some more annoyance: VScode uses **outdent**, but [Microsoft discourages it](https://learn.microsoft.com/nl-nl/style-guide/a-z-word-list-term-collections/i/indent-outdent). Democratically, Google reports **unindent** 1.1 million and **outdent** 31,6 million times. Best explanation (to use

[Github-comments] Re: [geany/geany] "Join Lines" doesn't explain the sequence of how the lines are joined. (Issue #3590)

2023-10-10 Thread Peter C. S. Scholtens via Github-comments
So the action is to **"Conc_atenate lines and remove white spaces (and tabs?)"**. I suggest to use the accelerator key `_a` as this is the most audible in spoken language. Also, would using `_U` not be more consistent in the same menu instead of **"U_ncomment Line(s)"** ? -- Reply to this

[Github-comments] Re: [geany/geany] Tooltip unclear: suggestion for better distinction between two options for backspace (Issue #3588)

2023-10-10 Thread Peter C. S. Scholtens via Github-comments
New attempt: "With the cursor inside an indentation, pressing backspace deletes this indentation level instead of deleting only a single character." -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/3588#issuecomment-1754632244 You are receiving this

[Github-comments] [geany/geany] "Join Lines" doesn't explain the sequence of how the lines are joined. (Issue #3590)

2023-10-10 Thread Peter C. S. Scholtens via Github-comments
The string "_Join Lines" doesn't explain the sequence of how the lines are joined. A description like "Concatenate Lines" would fit better I think. The strings are located at: - data/geany.glade:6938 - src/keybindings.c:508 -- Reply to this email directly or view it on GitHub:

[Github-comments] [geany/geany] Hyperlink in tooltip text can not be clicked. (Issue #3589)

2023-10-10 Thread Peter C. S. Scholtens via Github-comments
The following files (with line numbers) all contain hyperlinks in the text (to [this](https://docs.gtk.org/glib/method.DateTime.format.html) location), but cannot be clicked by the end-user. 1. data/geany.glade:5856 2. src/printing.c:279 3. src/ui_utils.c:729 4. plugins/saveactions.c:817 It

[Github-comments] [geany/geany] Tooltip unclear: suggestion for better distinction between two options for backspace (Issue #3588)

2023-10-10 Thread Peter C. S. Scholtens via Github-comments
The file **data/geany.glade** contains an unclear explanation of the option between either removal of an indent (removing possible multiple characters) or a character, see the property tooltip-text of **object class="GtkCheckButton"**, **id="check_backspace_unindent"**. Instead of _"With the

[Github-comments] [geany/geany] Update nl.po and some text suggestions (PR #3582)

2023-10-08 Thread Peter C. S. Scholtens via Github-comments
This is an update of the Dutch translation. Some suggestions for clarification of the original **msgid** texts: - As for end-users the subtle distinction between removal of an indent (removing possible multiple characters) or a character may be unclear, please clarify like With the cursor in

[Github-comments] Re: [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. 08c2ec6aa8606dc78c4925222791df5b52c6f578 Create main.md -- View it on GitHub: https://github.com/geany/geany/pull/3517/files/2f932671179d00b77f6a27e6474b40ac8a9ea2b1..08c2ec6aa8606dc78c4925222791df5b52c6f578 You are receiving this because you are subscribed to

[Github-comments] Re: [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. 2f932671179d00b77f6a27e6474b40ac8a9ea2b1 Delete file.md -- View it on GitHub: https://github.com/geany/geany/pull/3517/files/7fa7a9d5e6b29b43a925f27feca27a7b18b45120..2f932671179d00b77f6a27e6474b40ac8a9ea2b1 You are receiving this because you are subscribed to

[Github-comments] Re: [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
@peter-scholtens pushed 1 commit. 7fa7a9d5e6b29b43a925f27feca27a7b18b45120 Update Makefile.am -- View it on GitHub: https://github.com/geany/geany/pull/3517/files/d37d6a2020e31fb3ffcf8cb8c787a2f665a14655..7fa7a9d5e6b29b43a925f27feca27a7b18b45120 You are receiving this because you are

[Github-comments] Re: [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
Solved. After first `make install` with name `file.md` it never got removed, so I did that manually. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3517#issuecomment-1592957147 You are receiving this because you are subscribed to this thread. Message

[Github-comments] Re: [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
Yes, that was there. But I had renamed it from an earlier trial as `file.md` to `main.md`. No I see a Markdown template item in the pulldown menu, which however contains both of them `main.md` and `file.md`!? Like a kind of memory effect. -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
Locally I have the trailing backslash, and no space after that, git diff report: ``` @@ -103,6 +103,7 @@ template_files = \ templates/files/main.cxx \ templates/files/main.d \ templates/files/main.java \ + templates/files/main.md \ templates/files/main.py \

[Github-comments] Re: [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
I tried that, but it fails with: ```make[2]: *** No rule to make target 'templates/files/main.md', needed by 'all-am'. Stop.``` -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3517#issuecomment-1592928663 You are receiving this because you are

[Github-comments] [geany/geany] Create file.md (PR #3517)

2023-06-15 Thread Peter C. S. Scholtens via Github-comments
A small set of examples as reminders of how to use Markdown. Simply uploading this file is not sufficient, but it is unclear to me how the file ```data/Makefile``` can be generated to include the template, please help! You can view, comment on, or merge this pull request online at:

[Github-comments] [geany/geany] Update of 2018 edition of Rust (PR #3484)

2023-05-03 Thread Peter C. S. Scholtens via Github-comments
Some keywords added, as also the 128-bit integers, see: https://doc.rust-lang.org/reference/keywords.html You can view, comment on, or merge this pull request online at: https://github.com/geany/geany/pull/3484 -- Commit Summary -- * Update of 2018 edition of Rust -- File Changes --