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: Sun, 20 Nov 2022 08:30:58 +0200 [thread overview]
Message-ID: <83h6yu6st9.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SR5Ti=vmCk+GGDwbs1Q2cfAd5o0cMo8wrEL+2LAbFcuqw@mail.gmail.com> (message from Juanma Barranquero on Sat, 19 Nov 2022 21:58:21 +0100)
> From: Juanma Barranquero <lekktu@gmail.com>
> 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?
next prev parent reply other threads:[~2022-11-20 6:30 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
2022-11-19 20:58 ` Juanma Barranquero
2022-11-20 6:30 ` Eli Zaretskii [this message]
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=83h6yu6st9.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).