From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: JSON parsing of Extended ASCII Date: Tue, 10 May 2022 13:50:07 -0400 Message-ID: References: <4763d841-54f0-d146-d968-beb7988431ff@t-online.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35730"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Felix Weilbach Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 10 19:51:09 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1noU0r-00095t-Ao for ged-emacs-devel@m.gmane-mx.org; Tue, 10 May 2022 19:51:09 +0200 Original-Received: from localhost ([::1]:37468 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1noU0p-0001SO-Un for ged-emacs-devel@m.gmane-mx.org; Tue, 10 May 2022 13:51:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56762) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1noTzz-0000jP-Cj for emacs-devel@gnu.org; Tue, 10 May 2022 13:50:15 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:62915) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1noTzw-0006fK-7U for emacs-devel@gnu.org; Tue, 10 May 2022 13:50:13 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id C455B4427B1; Tue, 10 May 2022 13:50:10 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 76C904427AF; Tue, 10 May 2022 13:50:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1652205009; bh=kotcfODL4ffg4WMb8tuIkSfVzGhJ4av3KWXk7w4xr4Q=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=UTVv3MtDLQJS7bjRUbZeQwkHUj/hEBttBy+PHu4mk4P0JXA8MWtg7a0l46CtFumlQ Wu5ORCdA2q0lxkoSJVmrkhpyeVDriFSSq0QfMKzibjAid7+aMpim3NfoqGhsG5LTNM 7A8T8Wx9SJBHBuloi08bmrx8WBG1FjhHRtmMNxFRZ7p1Y7H8NvkPqM9YnedsT21/wl 6+MSL/GGqxNnN+zVwp/xMfqYxJew0rKRUo82knHfMHD2NsY7bIdLRsgttf3dWgKQV9 NfydpkllVPoKI8TGx6Qo6HQLzr3RszN9Du/AKDaOt/GbqQJgV50hFcW6hxAf4F5S2c bhlkCmlS430CQ== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 4BCA11209EC; Tue, 10 May 2022 13:50:09 -0400 (EDT) In-Reply-To: <4763d841-54f0-d146-d968-beb7988431ff@t-online.de> (Felix Weilbach's message of "Tue, 10 May 2022 19:18:37 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:289598 Archived-At: Felix Weilbach [2022-05-10 19:18:37] wrote: > I'm working on source code that has Extended ASCII characters inside > comments in it. This is unfortunate because LSP-mode crashes if it > encounters an invalid UTF-8 string. Please report it as a bug. It might be a bug in LSP-mode, or maybe in Emacs, or maybe in your LSP server, so as always, provide as many details as possible, starting with the actual error message (or even better a backtrace) as well as steps to (try and) reproduce the problem. Stefan