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>
See for instance what VLC does. (Or Audacity for that matter.)
Geany’s feature set is large enough (let alone accounting for
plugins) that it may warrant such an enhancement.
--
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/2848
In the Documentation generator menu the manual links to ```/usr/share/doc/geany-plugins/geanygendoc/html/manual.html``` and not ```/usr/share/doc/geany-plugin-gendoc/manual.html```.
This is in Geany 1.33-1 on Debian 10 (buster) in XFCE 4.12.5.
--
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-plugins/issues/992
I went through the various open PRs and open issues providing/requesting support of certain languages because some seem to be a bit neglected:
1. There's this PR adding Prolog support.
2. There's the Raku language support in #3169 which is hopefully in a mergable state.
3. I created #3647 (Scintilla lexer for JSON) and #3648 (Scintilla lexer for Nim) - for JSON there has already been a pull request in the past and they have also been requested in some open issues and in general I agree that when there's a Scintilla lexer, we should use it.
4. Yesterday I reviewed #3480 (CIL language support) and if the minor comments I had get addresses, I think it should be merged.
5. There are various open PRs and issues asking for Dart, LESS, and SCSS - these could be added as external filetypes. There should be no problem using C lexer for Dart and CSS lexer for LESS/SCSS (the CSS lexer supports LESS/SCSS modes).
What do you think?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3651
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3651(a)github.com>
I love Geany and use it all the time, but I was a little disappointed to find that CSS extension languages - such as Sass, SCSS and Less - do not have syntax highlighting
The userbase for these is probably small enough that new syntax highlighting rules specific to these languages would not be worthwhile, but to me it would make sense for the '.less' and '.scss' filename extensions to be recognised as CSS files (the same as '.css'); these languages are supersets of vanilla CSS (so the new features they add would still not receive highlighting, but most of the usual syntax highlighting one might expect would work)
Sass syntax is slightly different (uses indentation rather than braces a-la-Python) but still not a million miles from normal CSS.
--
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/2767
In ~/.config/geany/filetype_extensions.conf this could be added by default:
`CSS=*.css;*.less;`
In ~/.config/geany/filedefs/filetypes.css this could be added by default:
```
[lexer_properties]
lexer.css.less.language=1
```
--
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/1626
TOML is a fairly strictly defined configuration file syntax, used by various projects, supported by plenty of languages and already supported by some editors. I'm not familar with geany plugin dev (and lacking the time anyway) but maybe someone's interested in creating a syntax highlighting ruleset, similar to the INI config format.
https://github.com/toml-lang/toml
--
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/1268
This commit adds TOML configuration language support to Geany. It uses the recently merged Scintilla TOML lexer; for ctags parsing it uses the conf file parser which works reasonably well for TOML as well.
See https://github.com/ScintillaOrg/lexilla/pull/261
Fixes #1268
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3934
-- Commit Summary --
* Add TOML support
-- File Changes --
M data/Makefile.am (1)
A data/filedefs/filetypes.toml (57)
M data/filetype_extensions.conf (1)
M meson.build (1)
M scintilla/Makefile.am (1)
M scintilla/lexilla/include/SciLexer.h (16)
A scintilla/lexilla/lexers/LexTOML.cxx (486)
M scintilla/lexilla/src/Lexilla.cxx (2)
M scintilla/scintilla_changes.patch (1)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (11)
M src/highlightingmappings.h (27)
-- Patch Links --
https://github.com/geany/geany/pull/3934.patchhttps://github.com/geany/geany/pull/3934.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3934
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3934(a)github.com>