snippet support
not exactly a feature request, more of request to implement a feature (or whether to wait until extensions are supported). I've been working on what I hope will be a cross editor snippet manager ([link to project](https://github.com/skewballfox/sniper)) where the client and server are written in rust. while I'm looking to support a few features not covered in the specification (hoping to achieve eventual feature parity with [ultisnips](https://github.com/SirVer/ultisnips)), the syntax I'm working to support is a superset of the [syntax defined in the lsp specification](https://github.com/microsoft/language-server-protocol/blob/main/snippetSyntax.md). even with support for only basic dynamic snippets(ie vscode snippets), a major usecase is reducing the amount of effort to support snippets by emerging editors to defining the interface (similar to the benefit of the LSP). the project is at the point to where I can get completions per keystroke and insert/navigate snippets in vscode, but I'm depending on features specific to vscode. Working to support vscode first is also slowing me down because I really dislike/suck with javascript. I'm aware that [extension support is ongoing](https://github.com/helix-editor/helix/issues/122), but this also might be supportable by the editor itself (I'm trying to make it to where client implementation should be very little code) and also would make sense to a certain degree given that, while no language server (that I know of) handles sn
Posted by skewballfox on Jun 30, 2021, 6:54 PM
Tags
Related issues
- ⚠️ PHP CVEs. Update required!
- I think RTS could continue to work if someone made a massive leap of faith and put all the modern infra around it that a AAA extraction s...
- RFC: Pluggable SessionDB Provider — PostgreSQL, MySQL, and Beyond
- v2.1.113+ broken on Termux/Android: native binary requires glibc, no JS fallback
- I’m firmly anti-Tahoe and haven’t updated, and I’ve started to find Apple despicable.
- [FEATURE] Link a source control repo as the source for organization skills
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
reliability (Sysadmin)
⚠️ PHP CVEs. Update required!
I think RTS could continue to work if someone made a massive leap of faith and put all the modern infra around it that a AAA extraction s...
RFC: Pluggable SessionDB Provider — PostgreSQL, MySQL, and Beyond
v2.1.113+ broken on Termux/Android: native binary requires glibc, no JS fallback
I’m firmly anti-Tahoe and haven’t updated, and I’ve started to find Apple despicable.
[FEATURE] Link a source control repo as the source for organization skills
Feature Request: Option to disable paste text collapse in input field
We went down the WASM sandboxing rabbit hole at Gobii when building our agent infra.
snippet support
not exactly a feature request, more of request to implement a feature (or whether to wait until extensions are supported). I've been working on what I hope will be a cross editor snippet manager ([link to project](https://github.com/skewballfox/sniper)) where the client and server are written in rust. while I'm looking to support a few features not covered in the specification (hoping to achieve eventual feature parity with [ultisnips](https://github.com/SirVer/ultisnips)), the syntax I'm working to support is a superset of the [syntax defined in the lsp specification](https://github.com/microsoft/language-server-protocol/blob/main/snippetSyntax.md). even with support for only basic dynamic snippets(ie vscode snippets), a major usecase is reducing the amount of effort to support snippets by emerging editors to defining the interface (similar to the benefit of the LSP). the project is at the point to where I can get completions per keystroke and insert/navigate snippets in vscode, but I'm depending on features specific to vscode. Working to support vscode first is also slowing me down because I really dislike/suck with javascript. I'm aware that [extension support is ongoing](https://github.com/helix-editor/helix/issues/122), but this also might be supportable by the editor itself (I'm trying to make it to where client implementation should be very little code) and also would make sense to a certain degree given that, while no language server (that I know of) handles sn
Comments (0)
No comments yet. Start the discussion.