Hi.
I've been facing this issue for a couple of weeks now. My system is Manjaro Linux with Xfce 4.18 and I'm using Geany daily. (BTW I also have saved my Xfce user session to find back my windows where I want them to be).
I've noticed when I boot my system, sometimes, on random occasions, Geany's configuration has been overwritten with the defaults. It doesn't occur everytime I shut down my system, only randomly and _I haven't been able to find a pattern_. This is really annoying and the only way I've found so far is to restore my configuration from a backup.
I'm using a single F2FS filesystem on a NVMe drive, except for `/boot/efi`, which as required is located on a VFAT filesystem. I have no idea if this is important though. Geany is version 2.0, built 2023-10-23.
Cheers,
π
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3946
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3946(a)github.com>
This patch unifies the behavior of utils_write_file() with write_data_to_disk() so all 3 methods of file saving are supported.
From having a look at where this function is used, by Geany it's used only to store configuration files in the .config directory and some auxiliary functions like writing the export file by the exporter plugin. In the geany-plugins project this function is used only for saving configuration files.
Before this patch, by ignoring the default GIO file operation settings, the fwrite() method was used by default for saving configuration files which wasn't very safe and could lead to configuration file loss under some extreme conditions.
The documentation of this function was changed to reflect the situation better than now - the previous comment made the impression that file permissions were always preserved with this method but it wasn't the case and depended on the exact configuration. Technically this is an API change but since this function is used for saving configuration files only in practice, it should not be a problem.
See https://github.com/geany/geany/issues/3946 for more context.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3947
-- Commit Summary --
* Also use GIO when using utils_write_file()
-- File Changes --
M src/utils.c (24)
-- Patch Links --
https://github.com/geany/geany/pull/3947.patchhttps://github.com/geany/geany/pull/3947.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3947
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3947(a)github.com>
From having a look at where this function is used, by Geany it's used only to store configuration files in the .config directory and some auxiliary functions like writing the export file by the exporter plugin. In the geany-plugins project this function is used only for saving configuration files.
Before this patch, the fwrite() method was used by default for saving configuration files (because g_file_replace_contents() normally used by Geany wasn't used in this function) which wasn't very safe and could lead to configuration file loss under some extreme conditions.
The documentation of this function was changed to reflect the situation better than now - the previous comment made the impression that file permissions were always preserved with this method but it wasn't the case and depended on the exact configuration.
Replaces #3947.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3950
-- Commit Summary --
* Modify utils_write_file() to always use g_file_replace_contents()
-- File Changes --
M src/utils.c (69)
-- Patch Links --
https://github.com/geany/geany/pull/3950.patchhttps://github.com/geany/geany/pull/3950.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3950
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3950(a)github.com>
Funnily enough as I was trying to color the indent guides I found a bug with my bracketcolors plugin.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1221#issuecomment-2347381734
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1221/c2347381734(a)github.com>
> Good thing to ping it so "somebody" is reminded to try it and merge if they get a chance. Otherwise things get lost/forgotten, if it happens that nobody has time immediately, don't leave it nearly a year until the next ping.
Understood! Would someone be so kind as to approve my latest changes now?
With regards to the coloring the indent guides, I feel like it should be possible and I got pretty close but no dice yet.
Using the scintilla API I can quickly and easily infer what the indentation color should be, but using `SSM(sci, SCI_STYLESETFORE, STYLE_INDENTGUIDE, color)` sets the guide color for the entire document not just an indentation block.
Using indicators and `INDIC_BOX` I feel like I could probably implement the right half of this example but I personally think it looks ugly.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1221#issuecomment-2347373118
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1221/c2347373118(a)github.com>
The crosshatch (#) and asterisk (*) commands in Vim perform exact word searches. For example, with the cursor on "word", the asterisk would perform "/\<word\>" to search for the next exact occurrence of "word".
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1372
-- Commit Summary --
* Surround word with "\\<" and "\\>" for search_current().
-- File Changes --
M vimode/src/cmds/special.c (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1372.patchhttps://github.com/geany/geany-plugins/pull/1372.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1372
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1372(a)github.com>
After a few minutes editing, Geany freezes with cpu usage increasing to 100%. Force quit required.
System: Linux Mint 22
geany 2.0 (built on 2024-03-31 with GTK 3.24.41, GLib 2.80.0)
libgtk-3-0t64:amd64 3.24.41-4ubuntu1.1 amd64 installed
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3944
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3944(a)github.com>
This is a work-in-progress PR to add the LSP plugin. There are still some things missing like the documentation but in general the plugin should work. There are 3 modes of operation:
1. Without Geany LSP support
2. With basic LSP support using https://github.com/geany/geany/pull/3849
3. With full LSP support using https://github.com/geany/geany/pull/3850
The plugin should detect with which of these modes Geany was compiled and adjust itself automatically.
For the time being I still plan continue the main development of the plugin under https://github.com/techee/geany-lsp and sync the changes here from time to time.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1331
-- Commit Summary --
* Add LSP plugin
-- File Changes --
M Makefile.am (4)
M build/geany-plugins.nsi (1)
A build/lsp.m4 (10)
M configure.ac (1)
A lsp/AUTHORS (1)
A lsp/COPYING (340)
A lsp/ChangeLog (0)
A lsp/Makefile.am (4)
A lsp/NEWS (0)
A lsp/README (0)
A lsp/data/Makefile.am (5)
A lsp/data/lsp.conf (102)
A lsp/src/Makefile.am (119)
A lsp/src/json-glib/json-array.c (838)
A lsp/src/json-glib/json-builder.c (845)
A lsp/src/json-glib/json-builder.h (108)
A lsp/src/json-glib/json-debug.c (38)
A lsp/src/json-glib/json-debug.h (51)
A lsp/src/json-glib/json-enum-types.c (123)
A lsp/src/json-glib/json-enum-types.h (33)
A lsp/src/json-glib/json-gboxed.c (301)
A lsp/src/json-glib/json-generator.c (807)
A lsp/src/json-glib/json-generator.h (113)
A lsp/src/json-glib/json-glib.h (44)
A lsp/src/json-glib/json-gobject-private.h (36)
A lsp/src/json-glib/json-gobject.c (1005)
A lsp/src/json-glib/json-gobject.h (250)
A lsp/src/json-glib/json-gvariant.c (1346)
A lsp/src/json-glib/json-gvariant.h (50)
A lsp/src/json-glib/json-node.c (1555)
A lsp/src/json-glib/json-object.c (1261)
A lsp/src/json-glib/json-parser.c (1707)
A lsp/src/json-glib/json-parser.h (244)
A lsp/src/json-glib/json-path.c (998)
A lsp/src/json-glib/json-path.h (88)
A lsp/src/json-glib/json-reader.c (1138)
A lsp/src/json-glib/json-reader.h (161)
A lsp/src/json-glib/json-scanner.c (1371)
A lsp/src/json-glib/json-scanner.h (120)
A lsp/src/json-glib/json-serializable.c (386)
A lsp/src/json-glib/json-types-private.h (185)
A lsp/src/json-glib/json-types.h (534)
A lsp/src/json-glib/json-utils.c (95)
A lsp/src/json-glib/json-utils.h (37)
A lsp/src/json-glib/json-value.c (280)
A lsp/src/json-glib/json-version-macros.h (261)
A lsp/src/json-glib/json-version.h (100)
A lsp/src/jsonrpc-glib/jsonrpc-client.c (1752)
A lsp/src/jsonrpc-glib/jsonrpc-client.h (165)
A lsp/src/jsonrpc-glib/jsonrpc-glib.h (39)
A lsp/src/jsonrpc-glib/jsonrpc-input-stream-private.h (30)
A lsp/src/jsonrpc-glib/jsonrpc-input-stream.c (398)
A lsp/src/jsonrpc-glib/jsonrpc-input-stream.h (67)
A lsp/src/jsonrpc-glib/jsonrpc-marshalers.c (0)
A lsp/src/jsonrpc-glib/jsonrpc-marshalers.h (0)
A lsp/src/jsonrpc-glib/jsonrpc-message.c (0)
A lsp/src/jsonrpc-glib/jsonrpc-message.h (0)
A lsp/src/jsonrpc-glib/jsonrpc-output-stream.c (0)
A lsp/src/jsonrpc-glib/jsonrpc-output-stream.h (0)
A lsp/src/jsonrpc-glib/jsonrpc-server.c (0)
A lsp/src/jsonrpc-glib/jsonrpc-server.h (0)
A lsp/src/jsonrpc-glib/jsonrpc-version-macros.h (0)
A lsp/src/jsonrpc-glib/jsonrpc-version.h (0)
A lsp/src/lsp-autocomplete.c (0)
A lsp/src/lsp-autocomplete.h (0)
A lsp/src/lsp-code-lens.c (0)
A lsp/src/lsp-code-lens.h (0)
A lsp/src/lsp-command.c (0)
A lsp/src/lsp-command.h (0)
A lsp/src/lsp-diagnostics.c (0)
A lsp/src/lsp-diagnostics.h (0)
A lsp/src/lsp-format.c (0)
A lsp/src/lsp-format.h (0)
A lsp/src/lsp-goto-anywhere.c (0)
A lsp/src/lsp-goto-anywhere.h (0)
A lsp/src/lsp-goto-panel.c (0)
A lsp/src/lsp-goto-panel.h (0)
A lsp/src/lsp-goto.c (0)
A lsp/src/lsp-goto.h (0)
A lsp/src/lsp-highlight.c (0)
A lsp/src/lsp-highlight.h (0)
A lsp/src/lsp-hover.c (0)
A lsp/src/lsp-hover.h (0)
A lsp/src/lsp-log.c (0)
A lsp/src/lsp-log.h (0)
A lsp/src/lsp-main.c (0)
A lsp/src/lsp-progress.c (0)
A lsp/src/lsp-progress.h (0)
A lsp/src/lsp-rename.c (0)
A lsp/src/lsp-rename.h (0)
A lsp/src/lsp-rpc.c (0)
A lsp/src/lsp-rpc.h (0)
A lsp/src/lsp-semtokens.c (0)
A lsp/src/lsp-semtokens.h (0)
A lsp/src/lsp-server.c (0)
A lsp/src/lsp-server.h (0)
A lsp/src/lsp-signature.c (0)
A lsp/src/lsp-signature.h (0)
A lsp/src/lsp-symbol-kinds.c (0)
A lsp/src/lsp-symbol-kinds.h (0)
A lsp/src/lsp-symbol.c (0)
A lsp/src/lsp-symbol.h (0)
A lsp/src/lsp-symbols.c (0)
A lsp/src/lsp-symbols.h (0)
A lsp/src/lsp-sync.c (0)
A lsp/src/lsp-sync.h (0)
A lsp/src/lsp-utils.c (0)
A lsp/src/lsp-utils.h (0)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1331.patchhttps://github.com/geany/geany-plugins/pull/1331.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1331
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1331(a)github.com>