cygwin-x-doc/ug using.xml,1.7,1.8
Alexander Gottwald <xserver-commit-u7BhqnqprCWvj1b/[email protected]>
| Newsgroups | gmane.comp.freedesktop.xserver.cvs |
|---|---|
| Message-ID | <[email protected]> |
Committed by: ago Update of /cvs/xserver/cygwin-x-doc/ug In directory gabe:/tmp/cvs-serv1601/ug Modified Files: using.xml Log Message: 2004-12-29 Alexander Gottwald <[email protected]> * cg/programming-server-architecture.xml * faq/i18n.xml * ug/using.xml Fixed invalid characters. Replaced with proper entities. Index: using.xml =================================================================== RCS file: /cvs/xserver/cygwin-x-doc/ug/using.xml,v retrieving revision 1.7 retrieving revision 1.8 diff -u -d -r1.7 -r1.8 --- using.xml 2 Oct 2004 22:25:28 -0000 1.7 +++ using.xml 29 Dec 2004 18:57:07 -0000 1.8 @@ -64,7 +64,7 @@ <screen> &cygwin-bash-prompt; ~ -$ cd /usr/X11R6/bin && startx +$ cd /usr/X11R6/bin && startx </screen> <para>Or, you can run <command>startx</command> by first adding @@ -325,14 +325,14 @@ <listitem> <para>You can now launch remote X clients in your <command>ssh</command> session, for example, -<userinput>xterm&</userinput> will launch an xterm running on your +<userinput>xterm&</userinput> will launch an xterm running on your remote host that will display on your &project; screen.</para> </listitem> <listitem> <para>Launch other remote clients in the same manner. I recommend starting the remote clients in the background, by appending -<literal>&</literal> to the command name, so that you don't have to +<literal>&</literal> to the command name, so that you don't have to open several <command>ssh</command> sessions.</para> </listitem> @@ -392,14 +392,14 @@ <listitem> <para>You can now launch remote X clients in your <command>telnet</command> session, for example, -<userinput>xterm&</userinput> will launch an xterm running on your +<userinput>xterm&</userinput> will launch an xterm running on your remote host that will display on your &project; screen.</para> </listitem> <listitem> <para>Launch other remote clients in the same manner; I recommend starting the remote clients in the background, by appending -<literal>&</literal> to the command name, so that you don't have to +<literal>&</literal> to the command name, so that you don't have to open several <command>telnet</command> sessions.</para> </listitem>