unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* Coding systems in emacsclient (or, apostrophe's woes...)
@ 2022-11-19 19:13 Juanma Barranquero
  2022-11-19 19:39 ` Eli Zaretskii
  2022-11-19 19:40 ` Andreas Schwab
  0 siblings, 2 replies; 7+ messages in thread
From: Juanma Barranquero @ 2022-11-19 19:13 UTC (permalink / raw)
  To: Emacs developers

[-- Attachment #1: Type: text/plain, Size: 648 bytes --]

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

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).

Where is that change happening?

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

[-- Attachment #2: Type: text/html, Size: 1007 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Coding systems in emacsclient (or, apostrophe's woes...)
  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-19 19:40 ` Andreas Schwab
  1 sibling, 1 reply; 7+ messages in thread
From: Eli Zaretskii @ 2022-11-19 19:39 UTC (permalink / raw)
  To: Juanma Barranquero; +Cc: emacs-devel

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



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Coding systems in emacsclient (or, apostrophe's woes...)
  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 19:40 ` Andreas Schwab
  2022-11-19 20:59   ` Juanma Barranquero
  1 sibling, 1 reply; 7+ messages in thread
From: Andreas Schwab @ 2022-11-19 19:40 UTC (permalink / raw)
  To: Juanma Barranquero; +Cc: Emacs developers

On Nov 19 2022, Juanma Barranquero wrote:

> Where is that change happening?

Look for text-quoting-style.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Coding systems in emacsclient (or, apostrophe's woes...)
  2022-11-19 19:39 ` Eli Zaretskii
@ 2022-11-19 20:58   ` Juanma Barranquero
  2022-11-20  6:30     ` Eli Zaretskii
  0 siblings, 1 reply; 7+ messages in thread
From: Juanma Barranquero @ 2022-11-19 20:58 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

[-- Attachment #1: Type: text/plain, Size: 484 bytes --]

On Sat, Nov 19, 2022 at 8:39 PM Eli Zaretskii <eliz@gnu.org> wrote:

> By sheer coincidence, I've just fixed that a few minutes ago.

Great.

> That's quoting-style for you.

I didn't know about text-quoting-style.

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

[-- Attachment #2: Type: text/html, Size: 1001 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Coding systems in emacsclient (or, apostrophe's woes...)
  2022-11-19 19:40 ` Andreas Schwab
@ 2022-11-19 20:59   ` Juanma Barranquero
  2022-11-20  6:31     ` Eli Zaretskii
  0 siblings, 1 reply; 7+ messages in thread
From: Juanma Barranquero @ 2022-11-19 20:59 UTC (permalink / raw)
  To: Andreas Schwab; +Cc: Emacs developers

[-- Attachment #1: Type: text/plain, Size: 195 bytes --]

On Sat, Nov 19, 2022 at 8:40 PM Andreas Schwab <schwab@linux-m68k.org>
wrote:

> Look for text-quoting-style.

Thanks. I thought quoting style was for buffer content, not output of
message, etc.

[-- Attachment #2: Type: text/html, Size: 618 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Coding systems in emacsclient (or, apostrophe's woes...)
  2022-11-19 20:58   ` Juanma Barranquero
@ 2022-11-20  6:30     ` Eli Zaretskii
  0 siblings, 0 replies; 7+ messages in thread
From: Eli Zaretskii @ 2022-11-20  6:30 UTC (permalink / raw)
  To: Juanma Barranquero; +Cc: emacs-devel

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



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Coding systems in emacsclient (or, apostrophe's woes...)
  2022-11-19 20:59   ` Juanma Barranquero
@ 2022-11-20  6:31     ` Eli Zaretskii
  0 siblings, 0 replies; 7+ messages in thread
From: Eli Zaretskii @ 2022-11-20  6:31 UTC (permalink / raw)
  To: Juanma Barranquero; +Cc: schwab, emacs-devel

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 19 Nov 2022 21:59:39 +0100
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> > Look for text-quoting-style.
> 
> Thanks. I thought quoting style was for buffer content, not output of message, etc.

On the contrary, it is mostly used for messages and message-like buffers,
like *Help* etc.



^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2022-11-20  6:31 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2022-11-19 19:40 ` Andreas Schwab
2022-11-19 20:59   ` Juanma Barranquero
2022-11-20  6:31     ` Eli Zaretskii

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).