fix: escape literal $ in for-range snippets
#1181
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
skovhus
approved these changes
Jul 31, 2024
dezza
added a commit
to dezza/bash-language-server
that referenced
this pull request
Feb 26, 2025
Continuation and more complete version of bash-lsp#1181
|
Thanks. Replaced by #1258 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Unescaped, they make the snippets invalid; using the builtin snippet expansion from neovim, those two range snippets result in the error
...10.1/share/nvim/runtime/lua/vim/lsp/_snippet_grammar.lua:177: snippet parsing failed