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)
![geany_vertical](https://github.com/geany/geany/assets/7198614/c7864dcc-2e4c-4c55-9cf0-5aa8cb45c5d9)
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>
Previously the file path could be pasted in a file dialog.
With the new nice-looking OSX file dialog in Geany 1.36, this feature is no longer there. Standard behavior in OSX is "Command-Shift G" to bring up the path dialog. It would be super great if this expected OSX behavior was implemented also in Geany
--
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-osx/issues/14
Hello!
I'm a Twitch streamer and quite often on my streams I need to zoom in the text to a really large size for a better dramatic effect. But unfortunately Scintilla imposes a very strict limitation on zoom factor (from -10 to 20): https://www.scintilla.org/ScintillaDoc.html#SCI_ZOOMIN
And I don't really know why! If I remove the `SCI_ZOOMIN` limitation condition completely in [Scintilla itself](https://github.com/geany/geany/blob/77630564ad5446df89e9973f74bd378… it works just fine and does not degrade the performance or/and the stability of Geany.
![2021-02-17-183107_1382x1043_scrot](https://user-images.githubusercontent.com/165283/108199341-712c0f00-714f-11eb-9442-97dc37bccb88.png)
Would it be a good idea to remove the `SCI_ZOOMIN` limit completely (or at least dramatically increase it) and put that change into the `scintilla_changes.patch`? If yes, I could make a PR for that myself.
--
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/2750
I'm using Geany 1.38 in an Arch system with a LXQt DE and I would like to use the LXQt file chooser, which it's possible if the application uses [XDG desktop portal](https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.freedesktop.portal.FileChooser).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3458
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3458(a)github.com>
It would be great to have the ability to create multiple carets, select multiple pieces, or progressively clone a selection of a word to the next identical match creating multiple selections, not necessarily square, and then be able to type, delete, replace, etc. using the multiple carets until Esc is hit, pasting into all carets with Ctrl-V, and so on.
Here's an animated demonstration of these features: https://www.sublimetext.com/
This is Sublime Text's killer feature, and this would put Geany closer to one of the most reputed, feature rich commercial multiplatform editors, while still being free software. I believe there's support for this in Scintilla, at least to some extent.
This supersets #850.
---
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/1141
This patch adds a simple API allowing LSP plugins to take control of certain Geany built-in features and disabling their implementation in Geany. Currently, autocompletion, calltips, and going to definition/declaration is supported.
Plugins should define the Lsp struct, fill the pointers to the functions implementing the features they override, and register themselves using the lsp_register() call. Similarly, they should unregister themselves using lsp_unregister() when they don't want to provide the Lsp features any more, or, latest, when the plugin gets unloaded.
Each of the currently supported features is implemented using two functions - one checking whether Lsp plugin will override Geany's behavior of this feature, and the other function implementing the feature. For instance for autocompletion:
- autocomplete_available(doc) should return TRUE if the plugin performs autocompletion for the doc's filetype. This function is used to deactivate Geany's autocompletion when the Lsp plugin supports it.
- autocomplete_perform(doc) calls the corresponding interface of the LSP server (which responds asynchronously so when autocomplete_perform() is executed, the results won't be available yet)
The Lsp struct is padded with an array large enough to allow additions of many more functions to the struct and allowing binary compatibility with older LSP plugin versions not implementing all the functions. It's just mandatory that all plugins zero-initialize the allocated Lsp struct (either by creating it on the heap or by allocating it using g_new0() or similar function). NULL pointers in this struct are handled gracefully.
The current implementation supports only a single LSP plugin. However, if in the future arises the need for more LSP plugins running in parallel (e.g. a specialized LSP plugin for certain language together with the current "generic" LSP plugin), the implementation could be extended to support a list of Lsp structs and trying to call the functions defined by them one by one. The current interface should already be sufficient to support such an implementation.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3571
-- Commit Summary --
* Add API for LSP plugins
-- File Changes --
M meson.build (3)
M src/Makefile.am (2)
M src/editor.c (32)
M src/keybindings.c (11)
A src/lsp.c (107)
A src/lsp.h (59)
M src/symbols.c (9)
-- Patch Links --
https://github.com/geany/geany/pull/3571.patchhttps://github.com/geany/geany/pull/3571.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3571
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3571(a)github.com>
Insert devhelp plugin
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1311
-- Commit Summary --
* Porting devhelp plugin for gtk3. Working display in sidebar and main window. Missing showing SearchBar in sidebar or other tweaks.
* update of the files that make the devhelp-plugin be added to the geany IDE.
* try add SearchBar
* devhelp-plugin working
* library old and files some build artifacts deleted
* editing build file devhelp.m4
* webkit change to new version
* Changing the devhelp plugin maintainer in the MAINTAIN file
* replacing gtk_tool_button_new_from_stock with gtk_tool_button_new on zoom buttons and page forward and back buttons
* modified webkitgtk dependency in devhelp.m4 file
* Update build.yml
* Update build.yml
* Update build.yml
* Update build.yml
* changing webkit library in build.yml file and changing maintainer name in devhelp/README file
* changing webkit library in devhelp.m4
* changing webkit library in README
* insert devhelp plugin
-- File Changes --
M .github/workflows/build.yml (5)
M MAINTAINERS (7)
M Makefile.am (4)
M README (1)
A build/devhelp.m4 (29)
M configure.ac (1)
A devhelp/AUTHORS (1)
A devhelp/COPYING (674)
A devhelp/ChangeLog (0)
A devhelp/INSTALL (365)
A devhelp/Makefile.am (10)
A devhelp/NEWS (16)
A devhelp/README (114)
A devhelp/autogen.sh (6)
A devhelp/config.status (1863)
A devhelp/configure (5620)
A devhelp/configure.ac (34)
A devhelp/configure.scan (29)
A devhelp/data/Makefile.am (10)
A devhelp/data/devhelp-plugin-48.png (0)
A devhelp/data/devhelp-plugin.svg (467)
A devhelp/data/devhelp.conf (67)
A devhelp/data/geany-devhelp-plugin.png (0)
A devhelp/data/geany-devhelp.png (0)
A devhelp/data/home.html (16)
A devhelp/doc/Doxyfile (1630)
A devhelp/libtool (11748)
A devhelp/m4/libtool.m4 (8394)
A devhelp/m4/ltoptions.m4 (437)
A devhelp/m4/ltsugar.m4 (124)
A devhelp/m4/ltversion.m4 (23)
A devhelp/m4/lt~obsolete.m4 (99)
A devhelp/src/Makefile.am (40)
A devhelp/src/dhp-manpages.c (240)
A devhelp/src/dhp-object.c (1405)
A devhelp/src/dhp-plugin.c (230)
A devhelp/src/dhp-plugin.h (35)
A devhelp/src/dhp-settings.c (349)
A devhelp/src/dhp.h (144)
M po/POTFILES.in (46)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1311.patchhttps://github.com/geany/geany-plugins/pull/1311.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1311
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1311(a)github.com>