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

* effectively.sgml: Correct subject-verb agreement, missing verb

Browse Source 
(typo), preposition and (definite vs indefinite) article use.
This commit is contained in:
Christopher Faylor 2008-06-27 00:34:02 +00:00
parent 8b79fb163b
commit 3236e43753
2 changed files with 40 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
winsup/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2008-06-26 Fred Korz <korz_fred@emc.com>
* effectively.sgml: Correct subject-verb agreement, missing verb
(typo), preposition and (definite vs indefinite) article use.
2008-06-19 Christopher Faylor <me+cygwin@cgf.cx>
* faq-using.xml: Add more words about multiple cygwins.
@ -55,9 +60,9 @@
2006-08-25 Joshua Daniel Franklin <joshuadfranklin@yahoo.com>
* faq-setup.xml (faq.setup.uninstall): Mention Safe Mode
* faq-setup.xml (faq.setup.uninstall): Mention Safe Mode
requirement for accessing the Security tab in XP Home.
* faq-using.xml (faq.using.chmod): Mention FAT32.
* faq-using.xml (faq.using.chmod): Mention FAT32.
2006-08-09 Christopher Faylor <cgf@timesys.com>
@ -75,7 +80,7 @@
2006-06-01 Joshua Daniel Franklin <joshuadfranklin@yahoo.com>
* faq-setup.xml (faq.setup.automated): New FAQ.
* faq-setup.xml (faq.setup.automated): New FAQ.
2006-05-30 Dave Korn <dave.korn@artimi.com>
@ -753,7 +758,7 @@ Thu Jul 20 13:01:00 2000 Corinna Vinschen <corinna@vinschen.de>
Tue May 3 0:25:00 2000 Corinna Vinschen <corinna@vinschen.de>
* ntsec.sgml: Revisited description of `ntsec' according to
the changes in release 1.1.
* setup.sgml: Include ntsec.
* setup-net.sgml: Ditto.
* ntsec.sgml: Revisited description of `ntsec' according to
the changes in release 1.1.
* setup.sgml: Include ntsec.
* setup-net.sgml: Ditto.

10
winsup/doc/effectively.sgml
View File

@ -62,15 +62,15 @@ preferable to use <command>cygpath</command> in shell scripts.
<sect2> <title>Console Programs</title>
<para>
Another issue is receiving output from or giving input to the console-based
Another issue is receiving output from or giving input to console-based
Windows programs. Unfortunately, interacting with Windows console
applications is not a simple matter of using a translation utility. Windows
console applications and designed to run under <command>command.com</command>
console applications are designed to run under <command>command.com</command>
or <command>cmd.exe</command>, and some do not deal gracefully with other
situations. Cygwin can receive console input only if it
is also running in a console (DOS box) since Windows does not provide
any way to attach to the backend of the console device. Another
traditional Unix input/output method, ptys (pseudo-terminals), are
traditional Unix input/output method, ptys (pseudo-terminals), is
supported by Cygwin but not entirely by Windows. The basic problem is
that a Cygwin pty is a pipe and some Windows applications do not like
having their input or output redirected to pipes.
@ -80,8 +80,8 @@ having their input or output redirected to pipes.
To help deal with these issues, Cygwin supports customizable levels of
Windows verses Unix compatibility behavior. To be most compatible with
Windows programs, use a DOS prompt, running only the occasional Cygwin
command or script. Next would be to run <command>bash</command> with
the default DOS box. To make Cygwin more Unix compatible in this case,
command or script. Next would be to run <command>bash</command> within
a default DOS box. To make Cygwin more Unix compatible in this case,
set <envar>CYGWIN=tty</envar> (see <xref linkend="using-cygwinenv"></xref>).
Alternatively, the optional <systemitem>rxvt</systemitem> package provides
a native-Windows version of the popular X11 terminal emulator (it is not