zsh-workers
 help / color / mirror / code / Atom feed
From: Gary Oberbrunner <garyo@oberbrunner.com>
To: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
Cc: zsh-workers@sunsite.dk
Subject: Re: Zsh 4.0.4 and Emacs 21.1 in Windows XP
Date: Thu, 22 Nov 2001 21:38:51 -0500	[thread overview]
Message-ID: <3BFDB6BB.3070505@oberbrunner.com> (raw)
In-Reply-To: <000001c17348$9794de80$21c9ca95@mow.siemens.ru>

Borsenkow Andrej wrote:

>Probably, you are using native emacs and Cygwin zsh. In this case emacs
>writes pipe to zsh in text mode (CR-LF under DOS) and zsh reads it in
>binary mode (default for pipes under Cygwin). Please, look on
>www.cygwin.com for description of CYGWIN variable, specifically
>nobinmode. But I have no idea what effects may it have - it makes Cygwin
>read/write pipes in text (in DOS sense) mode which is O.K. for pure text
>but may break binary data.
>
>In general it is bad idea to mix native and Cygwin applications.
>
Yes, I think you nailed it here; my Emacs is compiled natively for 
Win32, and I guess zsh must be compiled with cygwin (I don't remember). 
 And what you describe above sounds like it could be the cause -- I've 
traced it quite thoroughly in emacs and it's definitely NOT sending a 
CR, only LF.  So it must be zsh/cygwin that's adding the CR.  Maybe I 
can add an option to zsh to strip off trailing CRs -- can anyone point 
me to where to start looking?  input.c maybe?

Thanks,

-- Gary Oberbrunner (garyo@genarts.com)


  reply	other threads:[~2001-11-23  2:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 19:59 Gary Oberbrunner
2001-11-22 11:26 ` Borsenkow Andrej
2001-11-23  2:38   ` Gary Oberbrunner [this message]
2001-11-23  6:05     ` Borsenkow Andrej
2001-11-23 15:48       ` Gary Oberbrunner
2001-11-23 22:09         ` Gary Oberbrunner
2001-11-23 21:21   ` Gary Oberbrunner
2001-11-26  7:32     ` Borsenkow Andrej
2001-11-26 15:31       ` Gary Oberbrunner
2002-02-08 15:20   ` Gary Oberbrunner
2001-11-22 11:35 ` Peter Stephenson

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=3BFDB6BB.3070505@oberbrunner.com \
    --to=garyo@oberbrunner.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).