public inbox for gentoo-doc-cvs@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Xavier Neys" <neysx@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: gpm.xml
Date: Tue, 26 Jul 2005 18:17:07 +0000	[thread overview]
Message-ID: <200507261817.j6QIHDV6019590@robin.gentoo.org> (raw)

neysx       05/07/26 18:17:07

  Modified:    xml/htdocs/doc/en gpm.xml
  Log:
  Coding style, removed installCD mention

Revision  Changes    Path
1.2       +51 -54    xml/htdocs/doc/en/gpm.xml

file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gpm.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gpm.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gpm.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo

Index: gpm.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gpm.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- gpm.xml	26 Jul 2005 17:56:59 -0000	1.1
+++ gpm.xml	26 Jul 2005 18:17:07 -0000	1.2
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gpm.xml,v 1.1 2005/07/26 17:56:59 jkt Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gpm.xml,v 1.2 2005/07/26 18:17:07 neysx Exp $ -->
 
 <guide link="/doc/en/gpm.xml">
 <title>Using a Mouse within the Console</title>
@@ -10,10 +10,9 @@
 </author>
 
 <abstract>
-This guide shows you how to set up and use gpm (the General
-Purpose Mouse server) from within a command line interface. 
-This is especially useful for new Gentoo installations or
-for systems that cannot or do not use an X server.
+This guide shows you how to set up and use gpm (the General Purpose Mouse
+server) from within a command line interface. This is especially useful for new
+Gentoo installations or for systems that cannot or do not use an X server.
 </abstract>
 
 <!-- The content of this document is licensed under the CC-BY-SA license -->
@@ -21,7 +20,7 @@
 <license/>
 
 <version>1.0</version>
-<date>2005-07-19</date>
+<date>2005-07-26</date>
 
 <chapter>
 <title>Getting gpm</title>
@@ -29,10 +28,10 @@
 <body>
 
 <p>
-If you've just installed Gentoo, you almost certainly don't have your mouse 
-set up to work within a command line interface (CLI) yet. Or perhaps you 
-can't use or don't need an X server, yet you still need to use a mouse. The 
-solution is simple: <c>gpm</c>, the General Purpose Mouse server.
+If you've just installed Gentoo, you almost certainly don't have your mouse set
+up to work within a command line interface (CLI) yet. Or perhaps you can't use
+or don't need an X server, yet you still need to use a mouse. The solution is
+simple: <c>gpm</c>, the General Purpose Mouse server.
 </p>
 
 <p>
@@ -44,8 +43,8 @@
 </pre>
 
 <p>
-You might have noticed a few messages during the compilation that warned 
-about configuring the server. You must do this before starting gpm.
+You might have noticed a few messages during the compilation that warned about
+configuring the server. You must do this before starting gpm.
 </p>
 
 </body>
@@ -58,9 +57,9 @@
 <body>
 
 <p>
-Before you can use gpm, you will need to uncomment the lines 
-corresponding to the location and protocol of your mouse. You do this by 
-editing the gpm configuration file:
+Before you can use gpm, you will need to uncomment the lines corresponding to
+the location and protocol of your mouse. You do this by editing the gpm
+configuration file:
 </p>
 
 <pre caption="Setting up gpm">
@@ -68,17 +67,17 @@
 </pre>
 
 <p>
-In my case, I have a USB mouse on <path>/dev/input/mouse0</path>. So, I 
-have uncommented <path>/dev/input/mice</path>, as this is the cumulative 
-device for all mice on the system, and the appropriate protocol. 
-Try using <path>/dev/input/mice</path> before <path>/dev/psaux</path>, as 
-the latter is deprecated and can be disabled in the latest 2.6 kernels. If 
-<path>/dev/input/mice</path> fails, then fall back to other devices. Here is 
-my example <path>/etc/conf.d/gpm</path>:
+In my case, I have a USB mouse on <path>/dev/input/mouse0</path>. So, I have
+uncommented <path>/dev/input/mice</path>, as this is the cumulative device for
+all mice on the system, and the appropriate protocol. Try using
+<path>/dev/input/mice</path> before <path>/dev/psaux</path>, as the latter is
+deprecated and can be disabled in the latest 2.6 kernels. If
+<path>/dev/input/mice</path> fails, then fall back to other devices. Here is my
+example <path>/etc/conf.d/gpm</path>:
 </p>
 
 <pre caption="Example gpm config">
-<comment># Please uncomment the type of mouse you have and the appropriate MOUSEDEV entry</comment>
+<comment>(Please uncomment the type of mouse you have and the appropriate MOUSEDEV entry)</comment>
 
 #MOUSE=ps2
 MOUSE=imps2
@@ -87,26 +86,25 @@
 </pre>
 
 <p>
-If you have a wheelmouse, you will want to use the imps2 protocol, so 
-uncomment that line. If imps2 and ps2 both fail to work for you, please
-refer to the gpm info page (<c>info gpm</c>) for other protocols to try. 
-Also, if you want to be able to click on hyperlinks in terminals to 
-navigate to a website, it is a good idea to follow the suggestion in the 
-<c>/etc/conf.d/gpm</c> file:
+If you have a wheelmouse, you will want to use the imps2 protocol, so uncomment
+that line. If imps2 and ps2 both fail to work for you, please refer to the gpm
+info page (<c>info gpm</c>) for other protocols to try. Also, if you want to be
+able to click on hyperlinks in terminals to navigate to a website, it is a good
+idea to follow the suggestion in the <c>/etc/conf.d/gpm</c> file:
 </p>
 
 <pre caption="Other options">
-<comment># Please uncomment this line if you want gpm to understand charsets</comment>
-<comment># used in URLs and names with ~ or : in them, etc.</comment>
-<comment># This is a good idea to turn on!</comment>
+<comment>(Please uncomment this line if you want gpm to understand charsets
+used in URLs and names with ~ or : in them, etc.
+This is a good idea to turn on!)</comment>
 
 APPEND="-l \"a-zA-Z0-9_.:~/\300-\326\330-\366\370-\377\""
 </pre>
 
 <p>
-The rest of the conf.d file contains other suggestions for your mouse server; 
-uncomment the various options according to your needs. See <c>man gpm</c> 
-for more information.
+The rest of the conf.d file contains other suggestions for your mouse server;
+uncomment the various options according to your needs. See <c>man gpm</c> for
+more information.
 </p>
 
 </body>
@@ -119,7 +117,7 @@
 <body>
 
 <p>
-Now that your mouse server is installed and configured, it's time to start 
+Now that your mouse server is installed and configured, it's time to start
 using it:
 </p>
 
@@ -128,9 +126,9 @@
 </pre>
 
 <p>
-You should see a block cursor appear. Remember that only root can run the gpm 
-init script. However, to avoid having to <c>su</c> and run the script every 
-single time you begin a new session, why not set gpm to begin every time you 
+You should see a block cursor appear. Remember that only root can run the gpm
+init script. However, to avoid having to <c>su</c> and run the script every
+single time you begin a new session, why not set gpm to begin every time you
 turn on your computer?
 </p>
 
@@ -139,8 +137,8 @@
 </pre>
 
 <p>
-Now, whenever you start your computer, you'll be greeted by the console cursor 
-by the time you get to the login prompt. The mouse server will continue to run 
+Now, whenever you start your computer, you'll be greeted by the console cursor
+by the time you get to the login prompt. The mouse server will continue to run
 even if you're not logged in as root.
 </p>
 
@@ -155,13 +153,13 @@
 <body>
 
 <p>
-Copying and pasting large blocks of text with a working mouse server is very 
-easy. Simply highlight the text with the left mouse button (it will stay 
-highlighted when you release the button), switch to a different terminal if you 
-wish, position the cursor, and press the middle mouse button to paste the text 
-where you placed the cursor. Note that you can copy and paste without ever 
+Copying and pasting large blocks of text with a working mouse server is very
+easy. Simply highlight the text with the left mouse button (it will stay
+highlighted when you release the button), switch to a different terminal if you
+wish, position the cursor, and press the middle mouse button to paste the text
+where you placed the cursor. Note that you can copy and paste without ever
 leaving the terminal you started. This makes posting the output of error
-messages  to the <uri link="http://forums.gentoo.org">Gentoo forums</uri>
+messages to the <uri link="http://forums.gentoo.org">Gentoo forums</uri>
 extremely simple.
 </p>
 
@@ -173,19 +171,18 @@
 
 <p>
 If you have a message on one screen and a text-mode web browser on the other,



-- 
gentoo-doc-cvs@gentoo.org mailing list



             reply	other threads:[~2005-07-26 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 18:17 Xavier Neys [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-26 18:28 [gentoo-doc-cvs] cvs commit: gpm.xml Jan Kundrat
2005-07-26 17:56 Jan Kundrat

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=200507261817.j6QIHDV6019590@robin.gentoo.org \
    --to=neysx@lark.gentoo.org \
    --cc=docs-team@lists.gentoo.org \
    --cc=gentoo-doc-cvs@lists.gentoo.org \
    /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