From: Richard Stallman <rms@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Process output truncation when using UTF-8
Date: Thu, 19 Jun 2003 23:15:47 -0400 [thread overview]
Message-ID: <E19TCNP-0002oB-6h@fencepost.gnu.org> (raw)
In-Reply-To: <200306190424.NAA22942@etlken.m17n.org> (message from Kenichi Handa on Thu, 19 Jun 2003 13:24:19 +0900 (JST))
The encoding routine correctly produces CR LF, but somehow
CR is converted to LF (perhaps by pty because the following
test works correctly).
Is it the pty and tty mechanism that does the conversion, perhaps?
next prev parent reply other threads:[~2003-06-20 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 8:12 Process output truncation when using UTF-8 Milan Zamazal
2003-05-30 8:16 ` Kenichi Handa
2003-06-03 14:59 ` Milan Zamazal
2003-06-04 12:48 ` Kenichi Handa
2003-06-13 10:38 ` Milan Zamazal
2003-06-19 4:24 ` Kenichi Handa
2003-06-20 3:15 ` Richard Stallman [this message]
2003-06-20 4:20 ` Kenichi Handa
2003-06-21 4:56 ` Richard Stallman
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=E19TCNP-0002oB-6h@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-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 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).