From: Yuri Khan <yuri.v.khan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: on eshell's encoding
Date: Wed, 27 Jul 2016 00:26:42 +0600 [thread overview]
Message-ID: <CAP_d_8UqLuSf5je3uHRjLM07MirvPjXhha6BHZhz4AE2F09pnQ@mail.gmail.com> (raw)
In-Reply-To: <83twfcs4j1.fsf@gnu.org>
On Wed, Jul 27, 2016 at 12:17 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> The only way to break the limitations of the
> system codepage is to use the Unicode (a.k.a. "wide") APIs, which
> expect strings in UTF-16 encoding. But that is not currently
> supported in Emacs, due to boring technical problems.
It’s not even clear if using the wide API on the caller side will
suffice. The callee also needs to cooperate, by using the
corresponding wide API to retrieve the command line arguments.
next prev parent reply other threads:[~2016-07-26 18:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 14:25 on eshell's encoding Daniel Bastos
2016-07-26 15:05 ` Eli Zaretskii
[not found] ` <mailman.2058.1469545530.26859.help-gnu-emacs@gnu.org>
2016-07-26 16:49 ` Daniel Bastos
2016-07-26 17:17 ` Eli Zaretskii
2016-07-26 18:26 ` Yuri Khan [this message]
2016-07-26 18:35 ` Eli Zaretskii
[not found] ` <mailman.2074.1469553449.26859.help-gnu-emacs@gnu.org>
2016-07-27 11:56 ` Daniel Bastos
2016-07-27 13:15 ` Yuri Khan
2016-07-27 16:22 ` Eli Zaretskii
2016-07-27 16:47 ` Yuri Khan
2016-07-27 17:12 ` Eli Zaretskii
2016-07-27 16:14 ` Eli Zaretskii
[not found] ` <mailman.2119.1469636078.26859.help-gnu-emacs@gnu.org>
2016-08-02 13:24 ` Daniel Bastos
2016-08-02 15:12 ` 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=CAP_d_8UqLuSf5je3uHRjLM07MirvPjXhha6BHZhz4AE2F09pnQ@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).