all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Re: Re: On Windows(R) Emacs «shell» mode doesn't prints an output.
Date: Thu, 25 Sep 2014 19:16:07 +0700	[thread overview]
Message-ID: <CAP_d_8W8LS5jVrXNLyNqqZhx5V=mnc1Fgns98iS_PDO=i8EVWQ@mail.gmail.com> (raw)
In-Reply-To: <83zjdoueui.fsf@gnu.org>

On Thu, Sep 25, 2014 at 6:19 PM, Eli Zaretskii <eliz@gnu.org> wrote:

>> [2]: http://www.siao2.com/2006/07/04/656051.aspx#comment-7971
>
> That's true, but you can work around that with wide (a.k.a. "Unicode")
> APIs, such as WriteConsoleW.  Not easy, but its doable; you can find
> the recipes and code on the Internet.

Sure but in that case chcp doesn’t affect you at all and is therefore
unnecessary.

> I think Western, Greek, and Cyrillic are covered, but CJK aren't, see
> http://www.microsoft.com/typography/fonts/font.aspx?FMID=1262.  So its
> coverage is mostly limited to European scripts.

Lucida Console is not the only font which is usable in the Windows
console. See, for example, MS Gothic:

http://www.microsoft.com/typography/fonts/font.aspx?FMID=2145



  reply	other threads:[~2014-09-25 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 20:07 On Windows(R) Emacs «shell» mode doesn't prints an output Hi-Angel
2014-09-25  7:43 ` Eli Zaretskii
2014-09-25  8:25   ` Yuri Khan
2014-09-25  8:44     ` Hi-Angel
2014-09-25  8:55     ` Eli Zaretskii
2014-09-25 10:18       ` Yuri Khan
2014-09-25 11:19         ` Eli Zaretskii
2014-09-25 12:16           ` Yuri Khan [this message]
2014-09-25 13:31             ` Eli Zaretskii
2014-09-25 15:44               ` Yuri Khan
2014-09-25 16:26                 ` 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

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

  git send-email \
    --in-reply-to='CAP_d_8W8LS5jVrXNLyNqqZhx5V=mnc1Fgns98iS_PDO=i8EVWQ@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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.