unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Coding systems in emacsclient (or, apostrophe's woes...)
Date: Sat, 19 Nov 2022 21:39:56 +0200	[thread overview]
Message-ID: <83r0xy7myb.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SS7eG=SUQSdwryA11ZvYB+_NcC-3kn5ZoqF8W2hN1pz0A@mail.gmail.com> (message from Juanma Barranquero on Sat, 19 Nov 2022 20:13:25 +0100)

> 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?



  reply	other threads:[~2022-11-19 19:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 19:13 Coding systems in emacsclient (or, apostrophe's woes...) Juanma Barranquero
2022-11-19 19:39 ` Eli Zaretskii [this message]
2022-11-19 20:58   ` Juanma Barranquero
2022-11-20  6:30     ` Eli Zaretskii
2022-11-19 19:40 ` Andreas Schwab
2022-11-19 20:59   ` Juanma Barranquero
2022-11-20  6:31     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83r0xy7myb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).