Uses the recently merged Zig lexer from lexilla.
Fixes #3724.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3974
-- Commit Summary --
* Add Zig support
-- File Changes --
M data/Makefile.am (3)
A data/filedefs/filetypes.zig (71)
M data/filetype_extensions.conf (1)
M meson.build (1)
M scintilla/Makefile.am (3)
M scintilla/lexilla/include/SciLexer.h (19)
A scintilla/lexilla/lexers/LexZig.cxx (465)
M scintilla/lexilla/src/Lexilla.cxx (3)
M scintilla/scintilla_changes.patch (1)
M src/editor.c (2)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (11)
M src/highlightingmappings.h (32)
-- Patch Links --
https://github.com/geany/geany/pull/3974.patchhttps://github.com/geany/geany/pull/3974.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3974
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3974(a)github.com>
The `/tmp` directory is delibery cleared by the operating system when booting and in the case of some operating systems also every few days. Geany cannot control the operating system behaviour, so files can disappear from `/tmp` in operating system removal. That is what it is intended for so that all the temporary files will be removed and the directory will not grow unacceptable large.
If your file isn't a temporary do not save it in the `/tmp` directory. You can set it somewhere else by setting the `Plugin Manager->Save Actions->Instance Save->Directory to save files in`. Note that the entry has a note that `/tmp` is the default and there is a note that if the files are saved elsewhere then the directory will continue to grow in size and you will have to manually clear it as the operating system won't clear it.
There is some alternative features in the save actions plugin #3911, but it is not merged, but you can try it. And even if it is merged for the next Geany version so far there is no documents so nobody will know about it.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/640#issuecomment-2463391797
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/640/2463391797(a)github.com>
Honestly, when you see that a file has been generated with a file name automatically by geany you don't think it will get deleted on reboot.
Why not change the default path to anything other than /tmp?
I've just lost some notes and it will happen to other users for sure
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/640#issuecomment-2462560372
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/640/2462560372(a)github.com>
Code snippets in README(.rst) should use ``` ``double backticks`` ``` rather than `` `single backticks` ``.
Otherwise it will just be escaped, but not preformatted as "code", making it hard to tell apart code from text in the README render (especially when it says stuff like "`` `code 1` or `code 2` ``").
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4029
-- Commit Summary --
* Fix README: highlight code as such using ``code``
-- File Changes --
M README (14)
-- Patch Links --
https://github.com/geany/geany/pull/4029.patchhttps://github.com/geany/geany/pull/4029.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4029
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4029(a)github.com>
If I make a mistake when making a series of changes in the selection, it is difficult to undo the changes and apply the correct changes: to undo a change I must refocus the edit pane; which removes the selection; forcing me to start over:
https://github.com/user-attachments/assets/34aecde7-be28-4769-bcf8-41ae4e63…
Please could the change dialog enable the user to undo or redo changes without losing the selection?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4032
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4032(a)github.com>
Starting Geany with --verbose (e.g. on the command line), should print debug and info log messages.
Presumably since ae01d30242 this does not work anymore except the user defines the environment variable "G_MESSAGES_DEBUG=all" before starting Geany.
We set this variable actually within Geany if the --verbose option is given (https://github.com/geany/geany/blob/master/src/libmain.c#L578C1-L578C5).
However, due to the change in ae01d30242 we initialize the encodings earlier and this initialization may emit its own log messages and so, I assume, the GLib logging system ignores the `G_MESSAGES_DEBUG` environment variable which we will set later in the startup process.
@b4n do you remember if it was necessary to initialize the encodings so early or can we maybe move it after https://github.com/geany/geany/blob/master/src/libmain.c#L1061 which would solve the issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4031
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4031(a)github.com>
this PR is adding the ctags for FORTH. It's very simple, it only detects the ":" for the beginning of a word:
Possible improvements:
- it could write "words" instead of "section" in the symbol list
- it could only parse the first word after the ":", and not the eventual code after it
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3377
-- Commit Summary --
* adding forth ctags
* adding forth.c for ctags
-- File Changes --
M ctags/Makefile.am (1)
M ctags/main/parsers_p.h (1)
A ctags/parsers/forth.c (78)
M src/filetypes.c (2)
M src/tagmanager/tm_parser.c (6)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/3377.patchhttps://github.com/geany/geany/pull/3377.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3377
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3377(a)github.com>
This would allow us to use e.g. meson or forth regex parsers. It possibly just means to add the parsers from the optilib directory but I haven't tried it yet.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4002
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4002(a)github.com>
This patch also updates update-ctags.py to update parsers in the optlib directory.
I'm not sure if the meson parser should use some icons for the groups in the sidebar or not, I chose the icon-free variant.
Fixes https://github.com/geany/geany/issues/4002
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4013
-- Commit Summary --
* Use Forth and Meson optlib-based ctags parsers
-- File Changes --
M ctags/Makefile.am (2)
A ctags/optlib/forth.c (76)
A ctags/optlib/meson.c (261)
M data/filedefs/filetypes.Meson.conf (1)
M meson.build (2)
M scripts/update-ctags.py (7)
M src/filetypes.c (2)
M src/tagmanager/tm_parser.c (36)
M src/tagmanager/tm_parser.h (2)
M src/tagmanager/tm_parsers.h (4)
-- Patch Links --
https://github.com/geany/geany/pull/4013.patchhttps://github.com/geany/geany/pull/4013.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4013
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4013(a)github.com>