unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: ROMMESWINKEL Hendrik <rommeswinkel@aoni.waseda.jp>
Cc: 71285@debbugs.gnu.org, "João Távora" <joaotavora@gmail.com>
Subject: bug#71285: 29.3; Emacs sends faulty notifications to texlab on unicode insert
Date: Sat, 01 Jun 2024 17:34:02 +0300	[thread overview]
Message-ID: <86mso4ohph.fsf@gnu.org> (raw)
In-Reply-To: <TYAPR01MB3198BCAB827B9ADD71AB750FF5FC2@TYAPR01MB3198.jpnprd01.prod.outlook.com> (message from ROMMESWINKEL Hendrik on Fri, 31 May 2024 04:33:27 +0000)

> From: ROMMESWINKEL Hendrik <rommeswinkel@aoni.waseda.jp>
> Date: Fri, 31 May 2024 04:33:27 +0000
> 
> Please see https://github.com/latex-lsp/texlab/issues/1130
> 
> Texlab crashes when inserting a unicode character such as BACK OF
> ENVELOPE
> 
> According to the Texlab maintainer, this is caused by a faulty
> notification:
> 
> ```
> {
>   "jsonrpc": "2.0",
>   "method": "textDocument/didChange",
>   "params": {
>     "textDocument": { "uri": "...", "version": 1 },
>     "contentChanges": [
>       {
>         "range": {
>           "start": { "line": 0, "character": 0 },
>           "end": { "line": 0, "character": 0 }
>         },
>         "rangeLength": 0,
>         "text": "🖂"
>       }
>     ]
>   }
> }
> ```

It looks like you are using lsp-mode or something?  If so, please
report that to the developers of lsp-mode.

If you use the built-in Eglot, then please tell more details, because
I don't quite see how this could have happened.





  reply	other threads:[~2024-06-01 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  4:33 bug#71285: 29.3; Emacs sends faulty notifications to texlab on unicode insert ROMMESWINKEL Hendrik
2024-06-01 14:34 ` Eli Zaretskii [this message]
2024-06-15  7:58   ` Eli Zaretskii
     [not found]     ` <TYAPR01MB319875BC5ECD8B59C3C8F1F0F5C32@TYAPR01MB3198.jpnprd01.prod.outlook.com>
2024-06-15 12:41       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86mso4ohph.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71285@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=rommeswinkel@aoni.waseda.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).