From: John Whitington <john@coherentgraphics.co.uk>
To: David Allsopp <dra-news@metastack.com>
Cc: "'Sylvain Le Gall'" <sylvain@le-gall.net>, <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Pipes and Standard Output / Input on Windows
Date: Mon, 2 Jun 2008 18:57:16 +0100 [thread overview]
Message-ID: <9BEAB9A5-5279-4054-A4E5-0A3382FDBD87@coherentgraphics.co.uk> (raw)
In-Reply-To: <F0DF2BE5FE824C179B5174C911101B48@countertenor>
On 2 Jun 2008, at 13:46, David Allsopp wrote:
>> It seems this is correct. See the section "Problems with Pipes" here:
>>
>> http://dev.mysql.com/doc/refman/5.0/en/windows-vs-unix.html
>
> See http://archives.postgresql.org/pgsql-hackers-win32/2005-01/msg00227.php
> for an equivalent Postgres post but with a solution :o)
>
> As I mentioned in my previous post, you need to use
> set_binary_mode_in and
> set_binary_mode_out on both stdin (to prevent ^Z ending the file)
> and stdout
> (to prevent \n being translated to \r\n). Having done this, I get no
> problems with ^Z characters in a test piping script. Does it fix your
> problem too?
This does indeed fix the problem here. Thanks!
--
John Whitington
Coherent Graphics Ltd
http://www.coherentpdf.com/
prev parent reply other threads:[~2008-06-02 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 13:39 John Whitington
2008-05-29 14:36 ` Sylvain Le Gall
2008-05-29 22:11 ` [Caml-list] " David Allsopp
2008-05-30 15:12 ` Sylvain Le Gall
2008-05-29 22:16 ` [Caml-list] " David Allsopp
2008-06-01 21:06 ` Sylvain Le Gall
2008-06-02 7:36 ` [Caml-list] " John Whitington
[not found] ` <4CA29E0FF2BC43FC9A7585F496BE65EF@countertenor>
2008-06-02 12:00 ` 'Sylvain Le Gall'
2008-06-02 12:46 ` David Allsopp
2008-06-02 17:57 ` John Whitington [this message]
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=9BEAB9A5-5279-4054-A4E5-0A3382FDBD87@coherentgraphics.co.uk \
--to=john@coherentgraphics.co.uk \
--cc=caml-list@inria.fr \
--cc=dra-news@metastack.com \
--cc=sylvain@le-gall.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.
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).