* Geany version: 2.0-2 "Pryce", built around 2024-11-01
* OS: Debian Sid
![image](https://github.com/user-attachments/assets/f9a0b678-d4cc-4ada-8f59-075e924e27d9)
Looking at the screenshot:
* Duplicated `(TFPSH.)WriteHelp`: the one with `TFPSH.` prefix (as it's a class function) points to the function implementation in the same file. One without the prefix points to the declaration as shown in the screenshot (inside the class's `private` section)
* We don't need to worry about `TFPSH.ProcessLine`, it has 2 overloads.
* But `that` symbol, which points to line 24. And line 24 is a comment line, which means the scanner should just ignore the entire line. This does not happen in C++ code.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4159
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4159(a)github.com>
I'm using Geany Nightly (Windows). I can't find it on Plugin Manager. I want to configure Geany to use Clangd for C/C++ code completion. Please help.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4082
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4082(a)github.com>
Anyone come across a JSpath, the HTML path, plugin?
This is the common, standard addressing identifying an element location in HTML document we often find anywhere, as opposed to less common Xpath.
Thanks before and please immediately feed information about it
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1299
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1299(a)github.com>
I can see the items in the list, but I can't select any of them.
p/s: Geany Nightly on Windows.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4158
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4158(a)github.com>
I imagine this is intentional, but just in case it is not.
I noticed that if you have a document that contains text in the last line number shown, when you go to save that document a new blank line automatically gets added to that document.
Does anyone know if this intentional? or something that needs to be corrected
Thank You
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4162
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4162(a)github.com>
See https://github.com/geany/geany/issues/4082
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1395
-- Commit Summary --
* Add LSP plugin
* Backport fixes from the geany-lsp project
* Sync to latest version from geany-lsp
* Sync with geany-lsp
* Drop unneeded writev() implementation from output stream
* Add missing headers to Makefile.am
* Sync with geany-lsp
* Sync with geany-lsp
* Attempt 1 to fix LSP on Windows
-- File Changes --
M Makefile.am (4)
M README (1)
M build/geany-plugins.nsi (1)
A build/lsp.m4 (39)
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 (288)
A lsp/data/Makefile.am (5)
A lsp/data/lsp.conf (534)
A lsp/deps/Makefile.am (78)
A lsp/deps/json-glib/json-array.c (838)
A lsp/deps/json-glib/json-builder.c (845)
A lsp/deps/json-glib/json-builder.h (108)
A lsp/deps/json-glib/json-debug.c (38)
A lsp/deps/json-glib/json-debug.h (51)
A lsp/deps/json-glib/json-enum-types.c (123)
A lsp/deps/json-glib/json-enum-types.h (33)
A lsp/deps/json-glib/json-gboxed.c (301)
A lsp/deps/json-glib/json-generator.c (807)
A lsp/deps/json-glib/json-generator.h (113)
A lsp/deps/json-glib/json-glib.h (44)
A lsp/deps/json-glib/json-gobject-private.h (36)
A lsp/deps/json-glib/json-gobject.c (1005)
A lsp/deps/json-glib/json-gobject.h (250)
A lsp/deps/json-glib/json-gvariant.c (1346)
A lsp/deps/json-glib/json-gvariant.h (50)
A lsp/deps/json-glib/json-node.c (1555)
A lsp/deps/json-glib/json-object.c (1261)
A lsp/deps/json-glib/json-parser.c (1707)
A lsp/deps/json-glib/json-parser.h (244)
A lsp/deps/json-glib/json-path.c (998)
A lsp/deps/json-glib/json-path.h (88)
A lsp/deps/json-glib/json-reader.c (1138)
A lsp/deps/json-glib/json-reader.h (161)
A lsp/deps/json-glib/json-scanner.c (1371)
A lsp/deps/json-glib/json-scanner.h (120)
A lsp/deps/json-glib/json-serializable.c (386)
A lsp/deps/json-glib/json-types-private.h (185)
A lsp/deps/json-glib/json-types.h (534)
A lsp/deps/json-glib/json-utils.c (95)
A lsp/deps/json-glib/json-utils.h (37)
A lsp/deps/json-glib/json-value.c (280)
A lsp/deps/json-glib/json-version-macros.h (261)
A lsp/deps/json-glib/json-version.h (100)
A lsp/deps/jsonrpc-glib/jsonrpc-client.c (1752)
A lsp/deps/jsonrpc-glib/jsonrpc-client.h (165)
A lsp/deps/jsonrpc-glib/jsonrpc-glib.h (39)
A lsp/deps/jsonrpc-glib/jsonrpc-input-stream-private.h (30)
A lsp/deps/jsonrpc-glib/jsonrpc-input-stream.c (0)
A lsp/deps/jsonrpc-glib/jsonrpc-input-stream.h (0)
A lsp/deps/jsonrpc-glib/jsonrpc-marshalers.c (0)
A lsp/deps/jsonrpc-glib/jsonrpc-marshalers.h (0)
A lsp/deps/jsonrpc-glib/jsonrpc-message.c (0)
A lsp/deps/jsonrpc-glib/jsonrpc-message.h (0)
A lsp/deps/jsonrpc-glib/jsonrpc-output-stream.c (0)
A lsp/deps/jsonrpc-glib/jsonrpc-output-stream.h (0)
A lsp/deps/jsonrpc-glib/jsonrpc-server.c (0)
A lsp/deps/jsonrpc-glib/jsonrpc-server.h (0)
A lsp/deps/jsonrpc-glib/jsonrpc-version-macros.h (0)
A lsp/deps/jsonrpc-glib/jsonrpc-version.h (0)
A lsp/src/Makefile.am (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-extension.c (0)
A lsp/src/lsp-extension.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-selection-range.c (0)
A lsp/src/lsp-selection-range.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-tree.c (0)
A lsp/src/lsp-symbol-tree.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)
A lsp/src/lsp-workspace-folders.c (0)
A lsp/src/lsp-workspace-folders.h (0)
A lsp/src/spawn/lspunixinputstream.c (0)
A lsp/src/spawn/lspunixinputstream.h (0)
A lsp/src/spawn/lspunixoutputstream.c (0)
A lsp/src/spawn/lspunixoutputstream.h (0)
A lsp/src/spawn/spawn.c (0)
A lsp/src/spawn/spawn.h (0)
M po/POTFILES.in (0)
M po/POTFILES.skip (0)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1395.patchhttps://github.com/geany/geany-plugins/pull/1395.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1395
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1395(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>
macOS Sequoia version: 15.2
![image](https://github.com/user-attachments/assets/7822f949-f243-4de6-8789-2aca4fc843d6)
UI interface is different with win11 version, and many functions can't use.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4161
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4161(a)github.com>
When you have "Line Numbers" visible, you can click on that line number to select the content on that entire line.
However, when you do this currently, it ends up selecting that entire line, but then it places the cursor on the next as well as the line highlight color if your theme has a color set for this.
There is probably a reason for this but to me it just seems a little visually confusing.
Suggesting maybe can add a setting to allow the cursor to end up at the end of that line numbers content, rather than placing the cursor on the following line.
You can also drag your left mouse button on multiple line numbers down to select multiple lines, which does the same where it moves the cursor to the next line number not clicked on.
If you try the opposite way, where you drag up to lines above, then it leaves the cursor at the beginning of the last line number you drag to.
Again this behavior may make sense the way that it is, but can just be a little visually confusing with the cursor and the line highlight color advancing to the next line.
Thank You
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/4150
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/4150(a)github.com>
I noticed that when opening QSS (QT Style Sheet) files in Geany that this format does not appear to be recognized by default. The files open, but do not show any syntax highlighting or support for keybindings to "comment" out lines of text for this format.
Being that I believe the syntax highlighting is the same as CSS which is already supported by Geany, would anyone consider adding the ability to support QSS as well?
I have never had to add a language before to Geany, I think in the past I read a little about this, so I imagine it is possible for user to do manually, but seems like this should be supported by default.
Thank You
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/4164
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/4164(a)github.com>