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.devel Subject: Re: Coding systems in emacsclient (or, apostrophe's woes...) Date: Sat, 19 Nov 2022 21:39:56 +0200 Message-ID: <83r0xy7myb.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35177"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 19 20:40:20 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 1owThM-00092Q-DQ for ged-emacs-devel@m.gmane-mx.org; Sat, 19 Nov 2022 20:40:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owTgs-0002Zl-TH; Sat, 19 Nov 2022 14:39:50 -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 1owTgr-0002Z0-Jr for emacs-devel@gnu.org; Sat, 19 Nov 2022 14:39:49 -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 1owTgr-0001Ur-BG; Sat, 19 Nov 2022 14:39:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=k8LvM7r+QrpYA7Nyf0KhnAVlh5Z4Et3PvU1eXVLRMJw=; b=TSHxwLSmkF6QA9hv/0EW NHXhoKPIvxRwuiKw2T0pAyE/5AKPrS2v1YOcU0MncmViWkAhCvnfI6bMOydQ6r7e33hud/uDUXvlW BcwrgsiHqc//8SVW25/E+gWtaonhqsONuLg/5t58ns2taWsVK2r2F6IxHD3DQ6a0cPlqyIhA+ekFX g6xv99BcPES6sYyXuD4d+yUGaoWZimWymBqgV8CZek4kiM4B5S9jZ4NwljtKnYIvOiA4N2l7aEo0y 9SQ8pjAP8fMZW7S5Uo8b2XitpDo4BLAVrCgS4GmMUND5Fn6IhfwoofogouhcBOGer3dJb0Brjgx1V 9CU8eBHq9iwhbA==; 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 1owTgq-0006ze-Rz; Sat, 19 Nov 2022 14:39:49 -0500 In-Reply-To: (message from Juanma Barranquero on Sat, 19 Nov 2022 20:13:25 +0100) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:300200 Archived-At: > From: Juanma Barranquero > Date: Sat, 19 Nov 2022 20:13:25 +0100 > > C:\> emacsclient --server-file=whatever --eval "(nonexistent)" > *ERROR*: Symbol’s function definition is VOID: nonexistent > > That's obviously UTF-8; if I change my console's codepage to 65001 > > *ERROR*: Symbol’s function definition is VOID: nonexistent By sheer coincidence, I've just fixed that a few minutes ago. > But that's not what puzzles me. What I don't understand is how that message is defined in data.c using an > APOSTROPE (#x27), but emacsclient is receiving a RIGHT SINGLE QUOTATION MARK (#x2019). That's quoting-style for you. > As an aside, perhaps it would be nice to have a way (a -coding command or whatever) for emacsclient to > tell server.el its output coding system... When is it not the locale-coding-system for messages and file-name-coding-system for file names?