JehanneOS
/
newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

* overview2.sgml: Remove CTRL-Z discussion. 

* cygwinenv.sgml: Expand on CYGWIN=binmode.
This commit is contained in:
Christopher Faylor 2002-12-19 02:14:06 +00:00
parent 037c11e868
commit c3405ba93e
3 changed files with 15 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2002-12-18 Christopher Faylor <cgf@redhat.com>
* overview2.sgml: Remove CTRL-Z discussion.
* cygwinenv.sgml: Expand on CYGWIN=binmode.
2002-11-10 Christopher Faylor <cgf@redhat.com>
* how-programming.texinfo: Document _WIN32 more fully.

12
winsup/doc/cygwinenv.sgml
View File

@ -10,9 +10,15 @@ by prefixing with <literal>no </literal>.</para>
<listitem>
<para><FirstTerm>(no)binmode</FirstTerm> - if set, non-disk
(e.g. pipe and COM ports) file opens default to binary mode
(no CR/LF/Ctrl-Z translations) instead of text mode.
Defaults to set (binary mode). This option must be set
before starting a Cygwin shell to have an effect on redirection.
(no CRLF translation) instead of text mode. Defaults to set (binary
mode). By default, devices are opened in binary mode, so this option
has little effect on normal cygwin operations.
It does affect two things, however. For non-NTFS filesystems, this
option will control the line endings for standard output/input/error
for redirection from the Windows command shell. It will also affect
the default translation mode of a pipe, although most shells set the
pipe to binary by default.
</para>
<warning><title>Warning!</title><para>If set in 12/98 b20.1, all files
always open in binary mode.</para></warning>

4
winsup/doc/overview2.sgml
View File

@ -171,9 +171,7 @@ sources.</para>
<para>Unfortunately, UNIX and Win32 use different end-of-line terminators in
text files. Consequently, carriage-return newlines have to be translated on
the fly by Cygwin into a single newline when reading in text mode. The
control-z character is interpreted as a valid end-of-file character for a
similar reason.</para>
the fly by Cygwin into a single newline when reading in text mode.</para>
<para>This solution addresses the compatibility requirement at the expense of
violating the POSIX standard that states that text and binary mode will be