[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Coding systems in emacsclient (or, apostrophe's woes...)
|
From: |
Eli Zaretskii |
|
Subject: |
Re: Coding systems in emacsclient (or, apostrophe's woes...) |
|
Date: |
Sat, 19 Nov 2022 21:39:56 +0200 |
> From: Juanma Barranquero <lekktu@gmail.com>
> 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?