From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Augusto Stoffel Newsgroups: gmane.emacs.bugs Subject: bug#61726: [PATCH] Eglot: Support positionEncoding capability Date: Fri, 24 Feb 2023 15:45:30 +0100 Message-ID: <874jrb9l6d.fsf@gmail.com> References: <87a614g628.fsf@gmail.com> <83cz60r7hu.fsf@gnu.org> <875ybsfvtj.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39588"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 61726@debbugs.gnu.org, =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Feb 24 15:46:23 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 1pVZL5-000A6G-SR for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 24 Feb 2023 15:46:23 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pVZKp-0006I9-RE; Fri, 24 Feb 2023 09:46:09 -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 1pVZKk-0006Hp-8V for bug-gnu-emacs@gnu.org; Fri, 24 Feb 2023 09:46:02 -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 1pVZKj-0002W2-Vj for bug-gnu-emacs@gnu.org; Fri, 24 Feb 2023 09:46:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pVZKj-00081Z-ON for bug-gnu-emacs@gnu.org; Fri, 24 Feb 2023 09:46:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Augusto Stoffel Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 24 Feb 2023 14:46: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.167724994130813 (code B ref 61726); Fri, 24 Feb 2023 14:46:01 +0000 Original-Received: (at 61726) by debbugs.gnu.org; 24 Feb 2023 14:45:41 +0000 Original-Received: from localhost ([127.0.0.1]:36482 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pVZKP-00080u-Bz for submit@debbugs.gnu.org; Fri, 24 Feb 2023 09:45:41 -0500 Original-Received: from mail-ed1-f42.google.com ([209.85.208.42]:40900) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pVZKN-00080f-6d for 61726@debbugs.gnu.org; Fri, 24 Feb 2023 09:45:39 -0500 Original-Received: by mail-ed1-f42.google.com with SMTP id i34so30341708eda.7 for <61726@debbugs.gnu.org>; Fri, 24 Feb 2023 06:45:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=yp8i6EoMEvTtaSt4Jv0hcYlB7SnUqvBODHFvvD+TDAw=; b=C/HDMaFI6i3hfTq5q0jxL7qpQqY62+XyVHkwoQd4WwtfpDESanc8lBhw2MLXQ9yNF7 d4W9JhQ1AgVH2k+icd1x2fp8HUTC+e5Za1LFdMu4KXkmCtuc//WiGi/kZIciD+CcvY9e Ry2C1EkMDYd3DNWoSOzqNK4FdV4Qyo9znYrOOp31VJJlLJuAgsRkUTypUDfv17EG9M1i bXAA5yJxnbKSK0tOVRIn8pnF1zMhAyG3uftkO72PsS8h57XkoI+FYmiRbov5vlCqDdKs JZHprF+CmVJ/w6mW41dB0M8SI5I/ShyQDNuWM1P+svOJuoZr7PuHhrpyJQlWuwOb6Yw0 aaag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:message-id:date:references:in-reply-to :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=yp8i6EoMEvTtaSt4Jv0hcYlB7SnUqvBODHFvvD+TDAw=; b=zil2w/4nUJ4VcwZLQ0SpFSAjFqpydNozNrkta5Quv8hR6MOdWkq8TqZo7X9K1NC2xj Yh45mWHhXMxl0wl/WNN01T5AhCDTxaT822qytLEp47BtpZZfXllTRcwxLo/Pqv7YTC7y uq557yVnU6mGNxFYcDtfgPQhrzKVg84OXzhZ59dgZh4t05J9aVE3UzLhFcWZub3/44p5 +e/qg9Eo8jW6oERfSUXHkCFUYwKWo5a5rSNxmnfwFgsQhKkhHoFj+ISEBgv/+nsDL9t9 TTPpUrZPDkvV9704slJLGDlL1MgVyhHD30XlSKCiBVYAvLA10q6pxIXkBcK1/U43TavJ 34fw== X-Gm-Message-State: AO0yUKXxIZQb/AL9DzYY7mj8uS5IDDLiIyElJMtrENfeHrL2CsHn9AI0 NWfA3mrLbZ4PhPxyMkTefzIIjyozq68= X-Google-Smtp-Source: AK7set9C5YXuR5+cbd6XF5WxsOwuRgWT+TYDYZl0vGOWqToN4okRJ8bd6mLn3V1ayJrISDKkvvlx/A== X-Received: by 2002:a17:907:97d5:b0:8eb:d3a5:b9f0 with SMTP id js21-20020a17090797d500b008ebd3a5b9f0mr9494611ejc.67.1677249932930; Fri, 24 Feb 2023 06:45:32 -0800 (PST) Original-Received: from ars3 ([2a02:8109:8ac0:56d0::6fd0]) by smtp.gmail.com with ESMTPSA id kq9-20020a170906abc900b008d9c518a318sm5730855ejb.142.2023.02.24.06.45.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Feb 2023 06:45:32 -0800 (PST) In-Reply-To: <83bkljnpck.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 24 Feb 2023 15:51:39 +0200") 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:256607 Archived-At: On Fri, 24 Feb 2023 at 15:51, Eli Zaretskii wrote: >> > > You can't even send or receive a message through the JSONRPC channel if >> > > it's not valid UTF-8 >> >> > That's because we _decided_ to behave like that. A decision that is >> > not carved in stone. >> >> At least or LSP, it seems it must be UTF-8: > > This is a misunderstanding: I didn't mean to say that we should send > invalid UTF-8 sequences. I meant something else. Quote from the rest > of my message: > >> > and `json-serialize' rightfully emits an error. >> >> There's no "rightfully" here. It's our decision to signal an error in >> this case. In fact, our decision was to follow the JSON specification, which says UTF-8 is the only allowed exchange encoding: https://www.rfc-editor.org/rfc/rfc8259#section-8.1 >> Substituting some innocent character for the unencodable >> ones would be an entirely legitimate alternative. So actually the answer here is no. You can save arbitrary bytes in a file in your laptop and call it data.json. But it you pass some data to someone else and promise it's in JSON format, then it _must_ be UTF-8 encoded.