To be removed from the C++ Standard Library in GCC 15.
https://gcc.gnu.org/gcc-15/porting_to.html
A heads-up. This is a backport of https://sourceforge.net/p/scintilla/code/ci/c7ffad21b23dfad4e8e9f36bb587acc… so would be included in a future Scintilla update.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4080
-- Commit Summary --
* scintilla: include cstdint
-- File Changes --
M scintilla/gtk/PlatGTK.cxx (1)
M scintilla/src/AutoComplete.cxx (1)
M scintilla/src/CallTip.cxx (1)
M scintilla/src/CellBuffer.cxx (1)
M scintilla/src/ChangeHistory.cxx (1)
M scintilla/src/Decoration.cxx (1)
M scintilla/src/Document.cxx (1)
M scintilla/src/Indicator.cxx (1)
M scintilla/src/KeyMap.cxx (1)
M scintilla/src/LineMarker.cxx (1)
M scintilla/src/PerLine.cxx (1)
M scintilla/src/Style.cxx (2)
M scintilla/src/ViewStyle.cxx (1)
M scintilla/src/XPM.cxx (1)
-- Patch Links --
https://github.com/geany/geany/pull/4080.patchhttps://github.com/geany/geany/pull/4080.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4080
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4080(a)github.com>
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.
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 realized I will need this signal for the LSP plugin as I ran into issues when Geany is shutting down. I'll try to explain what is going on here:
1. The jsonrpc-glib plugin uses glib asynchronous operations which require the main loop to run to send/receive messages.
2. When Geany is quitting, the main loop has no chance to run while https://github.com/geany/geany/blob/4c1191ac442e1bcceb60d7c2497e0baf5d5f4fa… is being executed.
3. The LSP plugin needs to terminate the LSP server processes gracefully when Geany is quitting by sending "shutdown" requests (and waiting for responses from the servers) followed by "exit" notifications. This currently happens inside plugin_cleanup() but because of (1) and (2) it has to run the main loop by itself (https://github.com/techee/geany-lsp/blob/3a31ec9be8323c668299d1c292b7c401f2…)
4. However, the side effect of running the main loop is that other events originating from Geany or plugins (such as various idle functions or timers) are processed by the main loop. These would normally never get executed and lead to unexpected things during shutdown (I did run into strange problems with #3911 because of this).
The bad thing here is that the main loop is run inside plugin_cleanup() and lots of things happen before it - projects and documents are closed (which emits lots of signals to which Geany or plugins react when the main loop is running), plugins are unloaded, etc.
To fix this, I'd like to move LSP server termination (and manual main loop running) to the point which is closer to the point where normal main loop runs and which is "calmer" and not affected by all the stuff happening during the shutdown process. This is the point where the "geany-before-quit" was added and the main loop would be run from its handler by the plugin. Even if some Geany events are still executed from it, it should be "normal" non-shutdown events that would get executed by the normal main loop too.
(Note that the fact that the main loop is running means that until all LSP servers are terminated, it would be possible to interact with the GUI of Geany. In practice though the termination is very fast so this isn't a real-world problem.)
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4069
-- Commit Summary --
* Add the geany-before-quit signal emitted before Geany is quitting
* Remove misleading main_status.quitting assignment
-- File Changes --
M doc/pluginsignals.c (10)
M src/geanyobject.c (6)
M src/geanyobject.h (1)
M src/libmain.c (4)
M src/plugindata.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/4069.patchhttps://github.com/geany/geany/pull/4069.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4069
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4069(a)github.com>