From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#61726: [PATCH] Eglot: Support positionEncoding capability Date: Fri, 24 Feb 2023 18:01:55 +0200 Message-ID: <83v8jrm4r0.fsf@gnu.org> References: <87a614g628.fsf@gmail.com> <831qmgr17p.fsf@gnu.org> <87wn48ecdz.fsf@gmail.com> <83v8jspgnr.fsf@gnu.org> <87lekodxja.fsf@gmail.com> <83a614p4sh.fsf@gnu.org> <87cz60dus9.fsf@gmail.com> <835ybrpnqj.fsf@gnu.org> <87y1oncz09.fsf@gmail.com> <83r0ufo3uc.fsf@gnu.org> <87356vbf0b.fsf@gmail.com> <83pm9znw0i.fsf@gnu.org> <87lekn9ss3.fsf@gmail.com> <83h6vbntqd.fsf@gnu.org> <878rgn9r6u.fsf@gmail.com> <83edqfnq5u.fsf@gnu.org> <83bkljnpck.fsf@gnu.org> <874jrb9l6d.fsf@gmail.com> <834jrbnlaf.fsf@gnu.org> <87v8jr83ic.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5138"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 61726@debbugs.gnu.org, joaotavora@gmail.com To: Augusto Stoffel Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Feb 24 17:03:19 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1pVaXX-00019Q-5t for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 24 Feb 2023 17:03:19 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pVaXI-00036B-Bl; Fri, 24 Feb 2023 11:03:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pVaXG-00035o-Nn for bug-gnu-emacs@gnu.org; Fri, 24 Feb 2023 11:03:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pVaXG-0001yW-FX for bug-gnu-emacs@gnu.org; Fri, 24 Feb 2023 11:03:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pVaXF-0002E2-VA for bug-gnu-emacs@gnu.org; Fri, 24 Feb 2023 11:03:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 24 Feb 2023 16:03:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61726 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 61726-submit@debbugs.gnu.org id=B61726.16772545238476 (code B ref 61726); Fri, 24 Feb 2023 16:03:01 +0000 Original-Received: (at 61726) by debbugs.gnu.org; 24 Feb 2023 16:02:03 +0000 Original-Received: from localhost ([127.0.0.1]:38001 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pVaWI-0002Cc-W7 for submit@debbugs.gnu.org; Fri, 24 Feb 2023 11:02:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:37412) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pVaWG-0002C9-SP for 61726@debbugs.gnu.org; Fri, 24 Feb 2023 11:02:01 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pVaWB-0008W3-HE; Fri, 24 Feb 2023 11:01:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=AlopVx0MXVQVyyz7du8LF1NMOGsoq9df69I1T39Nun4=; b=eXzUv2SFAG+y encQvkgvSX3sqoycfn9oTZ6u+LgMI92iApgBn2AZI5pmupzmenBPGv00pIbFfLpZsZukwS2c+2p0Q dvlnW0jz3+ydjpZzh+sd2ONtEJ3hjwFGgkGKV3v0WV272k9XVyzQ35fW25LMnHGoMMuA+GaGjK9Ed 4n7HAuR0+9Kh1vHJze+z4FHFRK9DqPRplTK+VvF8XL30kZWlP6Txo4dcmTaPVOCaPRTuG4skt5LCx hf9zEUovwlm+U+twYmuZglEenAKC1yhyBKhKoEEQH7DZgeJ1RQdHVzPlHX2lnsrJw+f5E+jzR7Pzw rcYi8F4CYvvtZ7EsxshAbQ==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pVaWA-00073Y-P3; Fri, 24 Feb 2023 11:01:55 -0500 In-Reply-To: <87v8jr83ic.fsf@gmail.com> (message from Augusto Stoffel on Fri, 24 Feb 2023 16:52:27 +0100) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:256627 Archived-At: > From: Augusto Stoffel > Cc: joaotavora@gmail.com, 61726@debbugs.gnu.org > Date: Fri, 24 Feb 2023 16:52:27 +0100 > > > abcde xyz > > > > where the \201 byte was replaced by the SPC character. The latter > > string is, of course, perfectly correct UTF-8 sequence, and so doesn't > > violate any specs. > > > > The SPC character as a replacement is, of course, just one example. > > We could instead use '?' or U+FFFD REPLACEMENT CHARACTER, or anything > > else, and all of those replacements can be encoded in UTF-8 without > > any problems. > > > > Did I make myself clear now? > > You made yourself clear the first time. What I don't understand is, why > do you think this is a good idea, because in my view it clearly isn't. > > So suppose we lie about the buffer content and say it's "abcde xyz". > Then the server sends a diagnostic saying "found unexpected space > character at column 6". What sense does it make to the user? How can that happen? Raw bytes can be in comments and in strings, and basically nowhere else in a program. How would the server decide that a space is not valid in these contexts? > Even worse, imagine we then request instructions to reformat the buffer. > Suppose that the replacement "abcde xyz" -> "abcde\nxyz" is meaningful > in our language but the replacement "abcde\201xyz" -> "abcde\nxyz" is > dangerous. Do we want to get into this kind of trouble? "Dangerous" in what way? And your objections/fears seem to circle around the special traits of the SPC character, so what if instead of SPC we use U+FFFD?