Difference between revisions of "Ideas for Google Summer of Code/Language Server Protocol"
Jump to navigation
Jump to search
Popcorndude (talk | contribs) m (formatting) |
|||
| Line 1: | Line 1: | ||
| + | |||
| + | |||
== Coding Challenge == |
== Coding Challenge == |
||
Write a trivial LSP server which receives requests from the editor and prints them to the terminal. |
Write a trivial LSP server which receives requests from the editor and prints them to the terminal. |
||
| + | |||
| + | == See also == |
||
| + | * https://github.com/apertium/apertium-lint Linting support for Apertium files |
||
| + | * https://github.com/apertium/tree-sitter-apertium Syntax highlight support for Apertium files. Many editors support tree-sitter grammars, e.g. Helix, Zed, Emacs, NeoVim, Lapce and Atom where it originated. But [https://github.com/Microsoft/vscode/issues/50140 VSCode does not] (without plugins), so the only easy way to get tree-sitter-support in a vscode plugin is via LSP. |
||
| + | * https://wiki.apertium.org/wiki/Emacs the various Emacs modes might give some inspiration for features |
||
[[Category:Ideas_for_Google_Summer_of_Code]] |
[[Category:Ideas_for_Google_Summer_of_Code]] |
||
Latest revision as of 09:27, 6 February 2024
Coding Challenge[edit]
Write a trivial LSP server which receives requests from the editor and prints them to the terminal.
See also[edit]
- https://github.com/apertium/apertium-lint Linting support for Apertium files
- https://github.com/apertium/tree-sitter-apertium Syntax highlight support for Apertium files. Many editors support tree-sitter grammars, e.g. Helix, Zed, Emacs, NeoVim, Lapce and Atom where it originated. But VSCode does not (without plugins), so the only easy way to get tree-sitter-support in a vscode plugin is via LSP.
- https://wiki.apertium.org/wiki/Emacs the various Emacs modes might give some inspiration for features
