Since many distros now distribute the GTK3 version of Geany the nightly builds should also check GTK3.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2003
The real name of the struct in Lua 5.1 is luaL_Reg. Lua 5.1 contains a define for compatibility, but it is not present in LuaJIT or later 5.x releases.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1231
-- Commit Summary --
* GeanyLua: Use luaL_Reg instead of luaL_reg
-- File Changes --
M geanylua/glspi_app.c (2)
M geanylua/glspi_dlg.c (2)
M geanylua/glspi_doc.c (2)
M geanylua/glspi_init.c (2)
M geanylua/glspi_kfile.c (2)
M geanylua/glspi_run.c (2)
M geanylua/glspi_sci.c (2)
M geanylua/gsdlg_lua.c (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1231.patchhttps://github.com/geany/geany-plugins/pull/1231.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1231
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1231(a)github.com>
On Windows, when I open a file, press Ctrl-L, and enter a relative path using forward slashes (`/`) instead of Windows's official backslash path separator (`\`), Geany doesn't understand that and produces a confusing error message.
Specifically, if I go to `C:\Users\cousteau\` and enter `AAA/BBB/ccc.txt`, I get "Error: couldn't find `C:\Users\cousteau\AAA\BBB\AAA\BBB\cc.txt`. Note that the directory part (`AAA/BBB/`) appears twice, but other than that it looks like Geany is somewhat able to parse the path. If instead I enter `AAA\BBB\ccc.txt`, Geany will open `C:\Users\cousteau\AAA\BBB\cc.txt` without complaining.
This is a bit inconveniencing because I often work with Unix-like environments (Git bash shell, MinGW, MSYS, WSL, tools and languages that ignore Windows's odd decision to use backslashes and use the usual `/` instead, etc), so whenever I get a file name (e.g. after running `find` on bash) the path is specified using forward slashes. I'd love to be able to just copy-paste that in Geany and have it open without manually replacing every `/` with `\`.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3868
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3868(a)github.com>
This PR contains some ctags updates which were made upstream as discussed in https://github.com/geany/geany/pull/3859.
Apart from that I noticed that the `update-ctags.py` script didn't copy the updated libreadtags library so I modified it to do so and as a result this PR also contains updated readtags.c/h which was missed in the previous PR.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3877
-- Commit Summary --
* update-ctags.py: Also copy the readtags library
* Update ctags to p6.1.20240519.0
* Add missing powershell mapping
* Update matlab unit test output
-- File Changes --
M ctags/libreadtags/readtags.c (298)
M ctags/libreadtags/readtags.h (20)
M ctags/main/repoinfo.h (2)
M ctags/parsers/jscript.c (96)
M ctags/parsers/matlab.c (11)
M ctags/parsers/pascal.c (11)
M ctags/parsers/powershell.c (35)
M scripts/update-ctags.py (4)
M src/tagmanager/tm_parser.c (1)
M tests/ctags/matlab_test.m.tags (4)
-- Patch Links --
https://github.com/geany/geany/pull/3877.patchhttps://github.com/geany/geany/pull/3877.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3877
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3877(a)github.com>
After opening Geany, or after creating a new tab in Geany, the default filetype is `None` and the default extension is null.
It will be quite useful to allow the user to specify a default filetype, or at least a default file extension when saving content in new Geany tabs.
A possible simple implementation would be allow the user to create `filetypes.None.conf` in which they could specify something like:
```
[settings]
# default extension used when saving files
extension=txt
```
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3847
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3847(a)github.com>
This is an experiment to use GtkFileChooserNative on Windows and macOS to address issues like
https://github.com/geany/geany-osx/issues/14
where the GTK dialogs don't offer the best user experience.
I kept using GtkFileChooser on Linux because it adds extra widgets to the dialog like file encoding and filetype selection and these aren't supported when using native dialogs. To me at least this isn't the most important thing and using native dialogs under Windows and macOS is more important IMO.
This leads to a few ifdefs in the code but I'd say the result isn't too bad (GtkFileChooser is a GtkWidget while GtkFileChooserNative isn't so some things have to differ). Before continuing with the save dialog and project open dialog, my question is whether something like that would be acceptable for Geany - @b4n @eht16 what do you think?
@eht16 Do the native dialogs work correctly on Windows with this patch? It seems to work alright on macOS.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3861
-- Commit Summary --
* Use GtkFileChooserNative for opening files on Windows and macOS
-- File Changes --
M src/dialogs.c (75)
-- Patch Links --
https://github.com/geany/geany/pull/3861.patchhttps://github.com/geany/geany/pull/3861.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3861
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3861(a)github.com>
Right now only the "document-save" is fired when performing "save as" which lacks the information about the original file name (which, for instance, is necessary for the LSP client where it needs to notify the server that the "old" document was closed and the document under the new name opened).
Right now the plugin at https://github.com/techee/geany-lsp has the code using this signal commented-out - I'll uncomment it once it's added to Geany (so renaming a file might cause problems synchronizing the document with the server with the current implementation).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3572
-- Commit Summary --
* Add "document-before-save-as" signal
-- File Changes --
M doc/pluginsignals.c (11)
M src/document.c (2)
M src/geanyobject.c (7)
M src/geanyobject.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/3572.patchhttps://github.com/geany/geany/pull/3572.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3572
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3572(a)github.com>
Make sure the gmo files are regenerated when the corresponding po files are updated, not to have stale translations after updating a po file.
This behavior most likely changed with the switch from GLib gettext infrastructure to to plain gettext one in 32977676a90244e0410524614757d2cf214bae43.
I had a hard time finding a rationale for the behavior of not automatically updating the gmo files when their source changed; all I could find is [this](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400453#24) which suggests it's intentional. Still, at least with our configuration of `PO_DEPENDS_ON_POT=no`, which means po files are not updated all the time, the point seems moot and does more harm than good.
Fix this by manually adding the correct dependency to the main target so the gmo files are updated automatically when the po changes. The only case where I can see it performing "useless" work is when calling update-po, which will effectively update all po files, and thus rebuild all gmo files. But that doesn't sound like any kind of problem, and rather expected.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3650
-- Commit Summary --
* Autotools: regenerate gmo files when po files are updated
-- File Changes --
A po/Rules-gmo (10)
-- Patch Links --
https://github.com/geany/geany/pull/3650.patchhttps://github.com/geany/geany/pull/3650.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3650
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3650(a)github.com>
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 [here.](https://github.com/geany/geany/issues/2540)
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3722
-- Commit Summary --
* Draft implementation of reload-all. Messy GUI and RESPONSE_DOCUMENT_RELOAD_ALL not handled correctly.
* Created bool unmodified_files_present to make gui button optional.
* Merge branch 'geany:master' into re-load-all
* Replaced fixed size number of button arguments with variable sized array of buttons (and responses) in document_show_message().
* Re-load All feature works functionally (but GUI needs re-work): detection if buffers are modified is built-in and user is offered a choice to reload all (and drop buffer modifications), reload only unmodified ones, or only the document in focus.
* Connected File->Re-load button and updated description.
* Switched to vertical buttons inside info_bar to avoid crowded Gtk-boxes.
-- File Changes --
M COMMITTERS (1)
M THANKS (2)
M data/geany.glade (11)
M src/callbacks.c (63)
M src/callbacks.h (2)
M src/dialogs.c (2)
M src/document.c (674)
M src/document.h (35)
M src/documentprivate.h (9)
M src/editor.c (4)
M src/keybindings.c (5)
M src/libmain.c (4)
-- Patch Links --
https://github.com/geany/geany/pull/3722.patchhttps://github.com/geany/geany/pull/3722.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3722
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3722(a)github.com>