public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: console vs pty (was: Re: First Pass at mintty documentation; 	etc.)
Date: Thu, 15 Jan 2009 06:54:00 -0000	[thread overview]
Message-ID: <20090115055917.GA19035@ednor.casa.cgf.cx> (raw)
In-Reply-To: <496ECD29.8010804@gmail.com>

On Thu, Jan 15, 2009 at 05:44:09AM +0000, Andy Koppe wrote:
>Chuck Wilson wrote:
>>"full screen" or "DOS" is a red herring.  Any program that does
>>something like the following, if compiled as a native program, won't
>>work in rxvt (or MinTTY, or cygwin/cmd-shell-with-CYGWIN=tty):
>>
>> #include <stdio.h>
>> main() {
>>   int c;
>>   while ((c = getc(stdin)) != EOF) fputc(c, stdout);
>> }
>>
>>The thing is, THIS program works as part of a pipeline even when
>>compiled as a native program -- but it breaks if you try to use it
>>interactively within rxvt/MinTTY/etc.  A cygwin-compiled version works
>>in all cases.
>
>I see, thanks for explaining that.  What exactly does happen when
>calling read() that means that pty input doesn't reach the program?

It's buffered differently.  MSVCRT thinks that Cygwin's ptys are pipes so
it buffers the input like a pipe rather than a terminal.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2009-01-15  6:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 21:39 First Pass at mintty documentation Lee D.Rothstein
2009-01-11 22:31 ` Andy Koppe
2009-01-11 23:03   ` Matt Wozniski
2009-01-12  4:30   ` Christopher Faylor
2009-01-12 18:25   ` First Pass at mintty documentation; etc Lee D. Rothstein
2009-01-14 23:37     ` Andy Koppe
2009-01-15  3:19       ` Andy Koppe
2009-01-15  6:03         ` console vs pty (was: Re: First Pass at mintty documentation; etc.) Andy Koppe
2009-01-15  6:54           ` Christopher Faylor [this message]
2009-01-16  6:55         ` First Pass at mintty documentation; etc Lee D. Rothstein
2009-01-16  9:57           ` Charles Wilson
2009-01-15  5:24       ` Andrew DeFaria
2009-01-15  5:44         ` Mark J. Reed
2009-01-15 12:34           ` Andrew DeFaria
2009-01-15 15:41             ` Mark J. Reed
2009-01-15  5:49         ` keycodes (was: Re: First Pass at mintty documentation; etc.) Andy Koppe
2009-01-15 12:43           ` keycodes Andrew DeFaria
2009-01-15 18:19             ` keycodes Matt Wozniski
2009-01-16 10:05               ` keycodes Andrew DeFaria
2009-01-15 15:51           ` keycodes (was: Re: First Pass at mintty documentation; etc.) Matt Wozniski
2009-01-16  5:20       ` First Pass at mintty documentation; etc Lee D. Rothstein

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=20090115055917.GA19035@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).