From: Jonathan Larmour <jlarmour@redhat.com>
To: k e <ndgipper@yahoo.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] RE: how to run the program
Date: Fri, 01 Sep 2000 03:58:00 -0000 [thread overview]
Message-ID: <39AF8BB6.B5FE9362@redhat.com> (raw)
In-Reply-To: <20000901021236.12025.qmail@web1103.mail.yahoo.com>
k e wrote:
>
> purpose: This is still a mystery, but it made scanf behave better.
> Without this, the buffer had to be filled before scanf returned.
> at: CYGSEM_LIBC_STDIO_WANT_BUFFERED_IO
> change: # user_value 1
> to: user_value 0
> also turned off _EXIT_FFLUSH to resolve conflict
I'm intrigued by this. What problem were you seeing? Was your terminal
emulator sending the correct EOL characters for the configuration of the
tty device?
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault
next prev parent reply other threads:[~2000-09-01 3:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-31 19:12 k e
2000-09-01 3:58 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-01 3:49 Andreas.Karlsson
2000-08-31 19:02 k e
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=39AF8BB6.B5FE9362@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=ndgipper@yahoo.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).