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: Sun, 20 Nov 2022 08:30:58 +0200 Message-ID: <83h6yu6st9.fsf@gnu.org> References: <83r0xy7myb.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4673"; 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 Sun Nov 20 07:31:21 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 1owdrM-00013L-OV for ged-emacs-devel@m.gmane-mx.org; Sun, 20 Nov 2022 07:31:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1owdqv-0004F2-0W; Sun, 20 Nov 2022 01:30:53 -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 1owdqt-0004Db-G6 for emacs-devel@gnu.org; Sun, 20 Nov 2022 01:30:51 -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 1owdqs-0004XT-UP; Sun, 20 Nov 2022 01:30:50 -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=fdKiM1A0pPB/ZbRGxmaMKnwY4E6On2ybzIur90Lpy1g=; b=fvgDQe32VgxI O1rcpGmCfEUosdnClNhXBltIGUHkHML82sGAagc0QOwGyKXGr7IxeOXNow92Bok+Q3KVS3QEhmqcN 01+rdGkNbgT+d6Uh7SjY2eAuKew6TF9w9S3U7kB1rTHgTkoZRkVqAMDJv0w9GofK+4sGf8BIY9Hlo V5CFg5BDKLFIvDm+06B4+MFfs+Rh7YrTXi4FooyLX60I059K92hEvbAMv+uPz89Ylazpj/07S+qgb WO0HXpz8qkvzInaMb5GlXVeGEcLF9FRuYuJUvV0XiQqY2F2TjxsVMdzStayheXCDGcgU6oENmCc68 Chi5NbKodSxKSLbA6XpTNg==; 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 1owdqs-0003lx-Fx; Sun, 20 Nov 2022 01:30:50 -0500 In-Reply-To: (message from Juanma Barranquero on Sat, 19 Nov 2022 21:58:21 +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:300225 Archived-At: > From: Juanma Barranquero > Date: Sat, 19 Nov 2022 21:58:21 +0100 > Cc: emacs-devel@gnu.org > > > When is it not the locale-coding-system for messages and file-name-coding-system > > for file names? > > I don't know. emacsclient can be used to talk to remote instances of Emacs. Do they know the > (locale|file-name)-coding system for the emacsclient that contacts them? If you are thinking about remote client connections, the solution for that is not easy. emacsclient is a relatively simple program that has none of the machinery we have in Emacs for determining the suitable encoding. How do you envision the client will know what encoding the server should use? If it cannot know that, how will it populate the new directive you have in mind?