From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org, Harald.Maier.BW@t-online.de, offby1@blarg.net
Subject: Re: Latin1 language environment breaks Cygwin shell buffer
Date: Sat, 06 Apr 2002 21:39:33 +0300 [thread overview]
Message-ID: <3791-Sat06Apr2002213932+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <m3vgb467vc.fsf@nyaumo.btinternet.com> (message from Jason Rumney on 06 Apr 2002 18:43:03 +0100)
> From: Jason Rumney <jasonr@gnu.org>
> Date: 06 Apr 2002 18:43:03 +0100
>
> "Eli Zaretskii" <eliz@is.elta.co.il> writes:
>
> > I suspect that the problem is with the EOL conversion in process I/O:
> > where w32-fns.el carefully sets up the EOL conversions as apropriate
> > for both input and output, the language environment leaves the EOL
> > conversion undecided.
>
> It only leaves the EOL conversion undecided when moving from
> "Default" to "Latin-1", which is the case that works. In the case
> of moving from "German" to "Latin-1", it sets both to iso-latin-1-dos.
I see in w32-fns that it sometimes sets the encode part of
default-process-coding-system to *-unix. Wasn't the problem in the
OP's case the DOS encoding of command lines sent to the shell?
next prev parent reply other threads:[~2002-04-06 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-30 16:32 Latin1 language environment breaks Cygwin shell buffer Eric Hanchrow
2002-03-30 18:10 ` Eli Zaretskii
2002-04-05 18:01 ` Harald.Maier.BW
[not found] ` <874rip963y.fsf@blarg.net>
2002-04-06 12:25 ` Harald.Maier.BW
2002-04-06 16:35 ` Jason Rumney
2002-04-06 17:27 ` Eli Zaretskii
2002-04-06 17:43 ` Jason Rumney
2002-04-06 18:39 ` Eli Zaretskii [this message]
2002-04-06 19:11 ` Jason Rumney
2002-04-06 23:02 ` Eric Hanchrow
2002-04-06 17:07 ` Eli Zaretskii
[not found] <873cyhsly5.fsf@blarg.net>
2002-03-31 6:08 ` Eli Zaretskii
2002-04-03 17:41 ` Jason Rumney
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=3791-Sat06Apr2002213932+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=Harald.Maier.BW@t-online.de \
--cc=bug-gnu-emacs@gnu.org \
--cc=offby1@blarg.net \
/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.