-
-
Notifications
You must be signed in to change notification settings - Fork 893
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix processing of multibyte messages #4519
Conversation
* Too many characters are read from back-to-back multibyte messages due to a conversion from byte-length to character length * Updated to immediately convert messages to unibyte when processing
Fixes #4250 |
lsp-mode.el
Outdated
@@ -7041,8 +7041,8 @@ server. WORKSPACE is the active workspace." | |||
leftovers body-length body chunk) | |||
(lambda (_proc input) | |||
(setf chunk (if (s-blank? leftovers) | |||
input | |||
(concat leftovers input))) | |||
(encode-coding-string input 'utf-8-unix) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: using the 3rd parameters of nocopy might be better due to we don't have to duplicate the string.
Can you check if it still working okay with that?
Any follow-ups? |
Hi, sorry, lost track of this. Can confirm that using the third param of |
@JeremyWeed same; I had forked your repository and rebased it with this one and seems like I have no issues anymore |
* Fix processing of multibyte messages * Too many characters are read from back-to-back multibyte messages due to a conversion from byte-length to character length * Updated to immediately convert messages to unibyte when processing * Update encoding logic to avoid copies --------- Co-authored-by: weedjer <[email protected]>
Too many characters are read from back-to-back multibyte messages due to a conversion from byte-length to character length
Updated to immediately convert messages to unibyte when processing