Whole buffer replaced with syntax error
See original GitHub issueIn this installation:
code --version
1.31.0
7c66f58312b48ed8ca4e387ebd9ffe9605332caa
x64
crystal-lang: 0.3.12
The entire buffer is replaced with any syntax error.
E.g.
my_method(
Syntax error in line 1: expecting token ')', not 'end'
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:15 (8 by maintainers)
Top Results From Across the Web
lsp-signature-mode replaces the whole source buffer with ...
Describe the bug When editing rust files (using rust-analyzer as an lsp server), the entire source code in the buffer occasionally gets ...
Read more >ud detected syntax error in fielded buffer #1 — oracle-tech
I am trying to access the TMIB in Tuxedo 10.3 on Linux. I have these env settings:
Read more >Custom C++ App returns "Syntax Error" when sending specific ...
1 Answer 1 ... I tried that as well before. by simply increasing the buffer by one more character, and adding '\n' the...
Read more >0980-read-exact - The Rust RFC Book
This RFC proposes adding its Read counterpart: a method (here called read_exact ) that reads a whole buffer, failing with an error (here...
Read more >Common SQL syntax errors and how to resolve them
In this article, we are going to describe some of the most common SQL syntax errors, and explains how you can resolve these...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In the meantime, I’ve published a fork with the fix from #99:
https://marketplace.visualstudio.com/items?itemName=jgillich.crystal-lang-fixed
Hi @jgillich @baelter @rowland @paulcsmith @girng @bcardiff vscode-crystal-lang is updated now.
I can confirm, this error doesn’t happen anymore, feel free to test it and report new issues 😄