</listitem>
<listitem>
-<para><envar>(no)envcache</envar> - If set, environment variable
-conversions (between Win32 and POSIX) are cached. Note that this may
-cause problems if the mount table changes, as the cache is not invalidated
-and may contain values that depend on the previous mount table
-contents. Defaults to set.</para>
-</listitem>
-
-<listitem>
<para><envar>(no)export</envar> - If set, the final values of these
settings are re-exported to the environment as <envar>CYGWIN</envar> again.
Defaults to off.</para>
</listitem>
<listitem>
-<para><envar>proc_retry:n</envar> - causes <function>fork()</function> and
-<function>exec*()</function> to retry n times when a child process fails
-due to certain windows-specific errors. These errors usually occur when
-processes are being started while a user is logging off.
-</para>
-</listitem>
-
-<listitem>
<para><envar>(no)glob[:ignorecase]</envar> - if set, command line arguments
containing UNIX-style file wildcard characters (brackets, question mark,
asterisk, escaped with \) are expanded into lists of files that match
</listitem>
<listitem>
-<para><envar>(no)reset_com</envar> - if set, serial ports are reset
-to 9600-8-N-1 with no flow control when used. This is done at open
-time and when handles are inherited. Defaults to set.</para>
-</listitem>
-
-<listitem>
-<para><envar>(no)strip_title</envar> - if set, strips the directory
-part off the window title, if any. Default is not set.</para>
-</listitem>
-
-<listitem>
-<para><envar>(no)title</envar> - if set, the title bar
-reflects the name of the program currently running. Default is not
-set.</para>
-</listitem>
-
-<listitem>
-<para><envar>(no)tty</envar> - if set, Cygwin enables extra support
-(i.e., termios) for UNIX-like ttys in the Windows console.
-It is not compatible with some Windows programs.
-Defaults to not set, in which case the tty is opened in text mode.
-Note that this has been changed such that ^D works as
-expected instead of ^Z, and is settable via <command>stty</command>.
-This option must be specified before starting a Cygwin shell
-and it cannot be changed in the shell. It should not be set when using
-other terminals (i.e., mintty or xterm).
+<para><envar>proc_retry:n</envar> - causes <function>fork()</function> and
+<function>exec*()</function> to retry n times when a child process fails
+due to certain windows-specific errors. These errors usually occur when
+processes are being started while a user is logging off.
</para>
</listitem>
<listitem>
-<para><envar>(no)upcaseenv</envar> - if set, Cygwin converts all
-environment variables to all-uppercase, when a Cygwin process is started
-from a non-Cygwin native Windows process. This was the default behavior in
-releases prior to Cygwin 1.7. If not set, Cygwin does not change the case
-of environment variables, except for a restricted set to maintain minimal
-backward compatibility and for correct handling of certain essential
-variables. The current list of always uppercased variables is:</para>
-<screen>
- ALLUSERSPROFILE
- COMMONPROGRAMFILES
- COMPUTERNAME
- COMSPEC
- HOME
- HOMEDRIVE
- HOMEPATH
- NUMBER_OF_PROCESSORS
- OS
- PATH
- PATHEXT
- PROCESSOR_ARCHITECTURE
- PROCESSOR_IDENTIFIER
- PROCESSOR_LEVEL
- PROCESSOR_REVISION
- PROGRAMFILES
- SYSTEMDRIVE
- SYSTEMROOT
- TEMP
- TERM
- TMP
- TMPDIR
- WINDIR
-</screen>
-<para>Defaults to not set.</para>
+<para><envar>(no)reset_com</envar> - if set, serial ports are reset
+to 9600-8-N-1 with no flow control when used. This is done at open
+time and when handles are inherited. Defaults to set.</para>
</listitem>
<listitem>
</listitem>
<listitem>
+<para><envar>(no)envcache</envar> - Originally, <envar>envcache</envar>
+controlled caching of environment variable conversion between Win32 and
+POSIX. The default setting works fine, the option was just useless.</para>
+</listitem>
+
+<listitem>
<para><envar>forkchunk:[intval]</envar> - This option allowed to influence
the <function>fork()</function> function in the way the memory of the
parent process gets copied to the child process. This functionality was
</listitem>
<listitem>
+<para><envar>(no)strip_title</envar> - Removed because setting the Window title
+can be controlled by the application via Escape sequences.</para>
+</listitem>
+
+<listitem>
+<para><envar>(no)title</envar> - Removed because setting the Window title
+can be controlled by the application via Escape sequences.</para>
+</listitem>
+
+<listitem>
<para><envar>(no)transparent_exe</envar> - This option has been removed
because the behaviour it switched on is now the standard behaviour in
Cygwin.</para>
complicates its usage so the option has been removed for now.</para>
</listitem>
+<listitem>
+<para><envar>(no)tty</envar> - If set, Cygwin enabled extra support
+(i.e., termios) for UNIX-like ttys in the Windows console. This option
+has been removed because it can be easily replaced by using a terminal
+like <command>mintty</command>, and it does not work well with some
+Windows programs.</para>
+</listitem>
+
+<listitem>
+<para><envar>(no)upcaseenv</envar> - This option could be used to convert
+all environment variables to uppercase. This was the default behavior in
+releases prior to Cygwin 1.7. Since keeping the case of environment
+variables intact is POSIXly correct, Cygwin now does not change the case
+of environment variables, except for a restricted set to maintain minimal
+backward compatibility. The current list of always uppercased variables is:
+</para>
+<screen>
+ ALLUSERSPROFILE
+ COMMONPROGRAMFILES
+ COMPUTERNAME
+ COMSPEC
+ HOME
+ HOMEDRIVE
+ HOMEPATH
+ NUMBER_OF_PROCESSORS
+ OS
+ PATH
+ PATHEXT
+ PROCESSOR_ARCHITECTURE
+ PROCESSOR_IDENTIFIER
+ PROCESSOR_LEVEL
+ PROCESSOR_REVISION
+ PROGRAMFILES
+ SYSTEMDRIVE
+ SYSTEMROOT
+ TEMP
+ TERM
+ TMP
+ TMPDIR
+ WINDIR
+</screen>
+</listitem>
+
</itemizedlist>
</sect2>
</sect2>
-<sect2 id="using-console"> <title>Console Programs</title>
-<para>
-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 are designed to run under
-<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 window 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), 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.
-</para>
-
-<para>
-To help deal with these issues, Cygwin supports customizable levels of
-Windows versus 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> 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>mintty</systemitem> package
-provides a terminal emulator similar to such X11 programs as
-<command>xterm</command> (it is not necessary to set
-<envar>CYGWIN=tty</envar> with <command>mintty</command> nor is it
-necessary to be running <systemitem>/Cygwin/X</systemitem>). Using
-<command>mintty.exe</command> provides the most Unix-like environment,
-but expect some compatibility problems with Windows programs.
-</para>
-
-</sect2>
-
<sect2 id="using-net"> <title>Cygwin and Windows Networking</title>
<para>
Many popular Cygwin packages, such as <systemitem>ncftp</systemitem>,