Spelling corrections to gnus manual

Spelling corrections to gnus manual

[Mike Pullen]

[-- Attachment #1: Type: text/plain, Size: 79 bytes --]

Someone please commit these spelling corrections to the gnus manual.

Thanks.


[-- Attachment #2: diff.out --]
[-- Type: application/octet-stream, Size: 22304 bytes --]

*** gnus.texi	Wed Jan  3 18:12:17 2001
--- gnus.texi.mtp	Wed Jan  3 23:03:46 2001
***************
*** 763,769 ****
  * Compilation::                How to speed Gnus up.
  * Mode Lines::                 Displaying information in the mode lines.
  * Highlighting and Menus::     Making buffers look all nice and cozy.
! * Buttons::                    Get tendonitis in ten easy steps!
  * Daemons::                    Gnus can do things behind your back.
  * NoCeM::                      How to avoid spam and other fatty foods.
  * Undo::                       Some actions can be undone.
--- 763,769 ----
  * Compilation::                How to speed Gnus up.
  * Mode Lines::                 Displaying information in the mode lines.
  * Highlighting and Menus::     Making buffers look all nice and cozy.
! * Buttons::                    Get tendinitis in ten easy steps!
  * Daemons::                    Gnus can do things behind your back.
  * NoCeM::                      How to avoid spam and other fatty foods.
  * Undo::                       Some actions can be undone.
***************
*** 1058,1064 ****
  me.  Usage of the patent (@dfn{Master/Slave Relationships In Computer
  Applications}) will be much more expensive, of course.)
  
! Anyways, you start one Gnus up the normal way with @kbd{M-x gnus} (or
  however you do it).  Each subsequent slave Gnusae should be started with
  @kbd{M-x gnus-slave}.  These slaves won't save normal @file{.newsrc}
  files, but instead save @dfn{slave files} that contain information only
--- 1058,1064 ----
  me.  Usage of the patent (@dfn{Master/Slave Relationships In Computer
  Applications}) will be much more expensive, of course.)
  
! Anyway, you start one Gnus up the normal way with @kbd{M-x gnus} (or
  however you do it).  Each subsequent slave Gnusae should be started with
  @kbd{M-x gnus-slave}.  These slaves won't save normal @file{.newsrc}
  files, but instead save @dfn{slave files} that contain information only
***************
*** 4597,4605 ****
  (@code{gnus-summary-mail-forward}).  If no prefix is given, the message
  is forwarded according to the value of (@code{message-forward-as-mime})
  and (@code{message-forward-show-mml}); if the prefix is 1, decode the
! message and forward directly inline; if the prefix is 2, foward message
  as an rfc822 MIME section; if the prefix is 3, decode message and
! forward as an rfc822 MIME section; if the prefix is 4, foward message
  directly inline; otherwise, the message is forwarded as no prefix given
  but use the flipped value of (@code{message-forward-as-mime}).  By
  default, the message is decoded and forwarded as an rfc822 MIME section.
--- 4597,4605 ----
  (@code{gnus-summary-mail-forward}).  If no prefix is given, the message
  is forwarded according to the value of (@code{message-forward-as-mime})
  and (@code{message-forward-show-mml}); if the prefix is 1, decode the
! message and forward directly inline; if the prefix is 2, forward message
  as an rfc822 MIME section; if the prefix is 3, decode message and
! forward as an rfc822 MIME section; if the prefix is 4, forward message
  directly inline; otherwise, the message is forwarded as no prefix given
  but use the flipped value of (@code{message-forward-as-mime}).  By
  default, the message is decoded and forwarded as an rfc822 MIME section.
***************
*** 4731,4739 ****
   If no prefix is given, the message is forwarded according to the value
  of (@code{message-forward-as-mime}) and
  (@code{message-forward-show-mml}); if the prefix is 1, decode the
! message and forward directly inline; if the prefix is 2, foward message
  as an rfc822 MIME section; if the prefix is 3, decode message and
! forward as an rfc822 MIME section; if the prefix is 4, foward message
  directly inline; otherwise, the message is forwarded as no prefix given
  but use the flipped value of (@code{message-forward-as-mime}).  By
  default, the message is decoded and forwarded as an rfc822 MIME section.
--- 4731,4739 ----
   If no prefix is given, the message is forwarded according to the value
  of (@code{message-forward-as-mime}) and
  (@code{message-forward-show-mml}); if the prefix is 1, decode the
! message and forward directly inline; if the prefix is 2, forward message
  as an rfc822 MIME section; if the prefix is 3, decode message and
! forward as an rfc822 MIME section; if the prefix is 4, forward message
  directly inline; otherwise, the message is forwarded as no prefix given
  but use the flipped value of (@code{message-forward-as-mime}).  By
  default, the message is decoded and forwarded as an rfc822 MIME section.
***************
*** 5184,5190 ****
  previous (unread) article, I'm sure there are people that want that as
  well.
  
! Multiply these five behaviours with five different marking commands, and
  you get a potentially complex set of variable to control what each
  command should do.
  
--- 5184,5190 ----
  previous (unread) article, I'm sure there are people that want that as
  well.
  
! Multiply these five behaviors with five different marking commands, and
  you get a potentially complex set of variable to control what each
  command should do.
  
***************
*** 5469,5475 ****
  Threading is done by looking at the @code{References} headers of the
  articles.  In a perfect world, this would be enough to build pretty
  trees, but unfortunately, the @code{References} header is often broken
! or simply missing.  Weird news propagation excarcerbates the problem,
  so one has to employ other heuristics to get pleasing results.  A
  plethora of approaches exists, as detailed in horrible detail in
  @pxref{Customizing Threading}.
--- 5469,5475 ----
  Threading is done by looking at the @code{References} headers of the
  articles.  In a perfect world, this would be enough to build pretty
  trees, but unfortunately, the @code{References} header is often broken
! or simply missing.  Weird news propagation exacerbates the problem,
  so one has to employ other heuristics to get pleasing results.  A
  plethora of approaches exists, as detailed in horrible detail in
  @pxref{Customizing Threading}.
***************
*** 6169,6175 ****
  To turn caching on, set @code{gnus-use-cache} to @code{t}.  By default,
  all articles ticked or marked as dormant will then be copied
  over to your local cache (@code{gnus-cache-directory}).  Whether this
! cache is flat or hierarchal is controlled by the
  @code{gnus-use-long-file-name} variable, as usual.
  
  When re-selecting a ticked or dormant article, it will be fetched from the
--- 6169,6175 ----
  To turn caching on, set @code{gnus-use-cache} to @code{t}.  By default,
  all articles ticked or marked as dormant will then be copied
  over to your local cache (@code{gnus-cache-directory}).  Whether this
! cache is flat or hierarchical is controlled by the
  @code{gnus-use-long-file-name} variable, as usual.
  
  When re-selecting a ticked or dormant article, it will be fetched from the
***************
*** 7242,7249 ****
  @findex gnus-article-strip-banner
  @cindex banner
  @cindex OneList
! @cindex stripping advertisments
! @cindex advertisments
  Strip the banner specified by the @code{banner} group parameter
  (@code{gnus-article-strip-banner}).  This is mainly used to hide those
  annoying banners and/or signatures that some mailing lists and moderated
--- 7242,7249 ----
  @findex gnus-article-strip-banner
  @cindex banner
  @cindex OneList
! @cindex stripping advertisements
! @cindex advertisements
  Strip the banner specified by the @code{banner} group parameter
  (@code{gnus-article-strip-banner}).  This is mainly used to hide those
  annoying banners and/or signatures that some mailing lists and moderated
***************
*** 7982,7988 ****
  default charsets to be used when reading these groups.
  
  In addition, some people do use soi-disant @sc{mime}-aware agents that
! aren't.  These blitely mark messages as being in @code{iso-8859-1} even
  if they really are in @code{koi-8}.  To help here, the
  @code{gnus-newsgroup-ignored-charsets} variable can be used.  The
  charsets that are listed here will be ignored.  The variable can be set
--- 7982,7988 ----
  default charsets to be used when reading these groups.
  
  In addition, some people do use soi-disant @sc{mime}-aware agents that
! aren't.  These blithely mark messages as being in @code{iso-8859-1} even
  if they really are in @code{koi-8}.  To help here, the
  @code{gnus-newsgroup-ignored-charsets} variable can be used.  The
  charsets that are listed here will be ignored.  The variable can be set
***************
*** 9742,9748 ****
  @end lisp
  
  You can, however, use any mail select method (@code{nnml},
! @code{nnmbox}, etc.).  @code{nnfolder} is a quite likeable select method
  for doing this sort of thing, though.  If you don't like the default
  directory chosen, you could say something like:
  
--- 9742,9748 ----
  @end lisp
  
  You can, however, use any mail select method (@code{nnml},
! @code{nnmbox}, etc.).  @code{nnfolder} is a quite likable select method
  for doing this sort of thing, though.  If you don't like the default
  directory chosen, you could say something like:
  
***************
*** 10165,10171 ****
  complicated---say, for instance, that you want to read from the
  @sc{nntp} server @samp{news.funet.fi} on port number 13, which
  hangs if queried for @sc{nov} headers and has a buggy select.  Ahem.
! Anyways, if you had to specify that for each group that used this
  server, that would be too much work, so Gnus offers a way of naming
  select methods, which is what you do in the server buffer.
  
--- 10165,10171 ----
  complicated---say, for instance, that you want to read from the
  @sc{nntp} server @samp{news.funet.fi} on port number 13, which
  hangs if queried for @sc{nov} headers and has a buggy select.  Ahem.
! Anyway, if you had to specify that for each group that used this
  server, that would be too much work, so Gnus offers a way of naming
  select methods, which is what you do in the server buffer.
  
***************
*** 10284,10290 ****
  @findex gnus-server-regenerate-server
  Request that the server regenerate all its data structures
  (@code{gnus-server-regenerate-server}).  This can be useful if you have
! a mail backend that has gotten out of synch.
  
  @end table
  
--- 10284,10290 ----
  @findex gnus-server-regenerate-server
  Request that the server regenerate all its data structures
  (@code{gnus-server-regenerate-server}).  This can be useful if you have
! a mail backend that has gotten out of sync.
  
  @end table
  
***************
*** 10779,10785 ****
  Opens a connection to a server over a @dfn{secure} channel.  To use this
  you must have SSLay installed
  (@uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL}, and you also need
! @file{ssl.el} (from the W3 distributeion, for instance).  You then
  define a server as follows:
  
  @lisp
--- 10779,10785 ----
  Opens a connection to a server over a @dfn{secure} channel.  To use this
  you must have SSLay installed
  (@uref{ftp://ftp.psy.uq.oz.au/pub/Crypto/SSL}, and you also need
! @file{ssl.el} (from the W3 distribution, for instance).  You then
  define a server as follows:
  
  @lisp
***************
*** 10858,10864 ****
  @item nntp-record-commands
  @vindex nntp-record-commands
  If non-@code{nil}, @code{nntp} will log all commands it sends to the
! @sc{nntp} server (along with a timestep) in the @samp{*nntp-log*}
  buffer.  This is useful if you are debugging a Gnus/@sc{nntp} connection
  that doesn't seem to work.
  
--- 10858,10864 ----
  @item nntp-record-commands
  @vindex nntp-record-commands
  If non-@code{nil}, @code{nntp} will log all commands it sends to the
! @sc{nntp} server (along with a timestamp) in the @samp{*nntp-log*}
  buffer.  This is useful if you are debugging a Gnus/@sc{nntp} connection
  that doesn't seem to work.
  
***************
*** 10875,10881 ****
  contain very big articles---@samp{alt.binaries.pictures.furniture}, for
  instance.
  
! Anyways, you just specify @code{nnspool} as the method and @code{""} (or
  anything else) as the address.
  
  If you have access to a local spool, you should probably use that as the
--- 10875,10881 ----
  contain very big articles---@samp{alt.binaries.pictures.furniture}, for
  instance.
  
! Anyway, you just specify @code{nnspool} as the method and @code{""} (or
  anything else) as the address.
  
  If you have access to a local spool, you should probably use that as the
***************
*** 13957,13963 ****
  this concept of marking articles @code{Deleted} which doesn't actually
  delete them, and this (marking them @code{Deleted}, that is) is what
  nnimap does when you delete a article in Gnus (with @kbd{G DEL} or
! similair).
  
  Since the articles aren't really removed when we mark them with the
  @code{Deleted} flag we'll need a way to actually delete them.  Feel like
--- 13957,13963 ----
  this concept of marking articles @code{Deleted} which doesn't actually
  delete them, and this (marking them @code{Deleted}, that is) is what
  nnimap does when you delete a article in Gnus (with @kbd{G DEL} or
! similar).
  
  Since the articles aren't really removed when we mark them with the
  @code{Deleted} flag we'll need a way to actually delete them.  Feel like
***************
*** 13972,13978 ****
  @table @code
  
  @item always
! The default behaviour, delete all articles marked as "Deleted" when
  closing a mailbox.
  @item never
  Never actually delete articles.  Currently there is no way of showing
--- 13972,13978 ----
  @table @code
  
  @item always
! The default behavior, delete all articles marked as "Deleted" when
  closing a mailbox.
  @item never
  Never actually delete articles.  Currently there is no way of showing
***************
*** 14098,14104 ****
  
  This variable can also have a function as its value, the function will
  be called with the headers narrowed and should return a group where it
! thinks the article should be splitted to.  See @code{nnimap-split-fancy}.
  
  The splitting code tries to create mailboxes if it need too.
  
--- 14098,14104 ----
  
  This variable can also have a function as its value, the function will
  be called with the headers narrowed and should return a group where it
! thinks the article should be split to.  See @code{nnimap-split-fancy}.
  
  The splitting code tries to create mailboxes if it need too.
  
***************
*** 14129,14135 ****
  @vindex nnimap-split-predicate
  
  Mail matching this predicate in @code{nnimap-split-inbox} will be
! splitted, it is a string and the default is @samp{UNSEEN UNDELETED}.
  
  This might be useful if you use another @sc{imap} client to read mail in
  your inbox but would like Gnus to split all articles in the inbox
--- 14129,14135 ----
  @vindex nnimap-split-predicate
  
  Mail matching this predicate in @code{nnimap-split-inbox} will be
! split, it is a string and the default is @samp{UNSEEN UNDELETED}.
  
  This might be useful if you use another @sc{imap} client to read mail in
  your inbox but would like Gnus to split all articles in the inbox
***************
*** 14639,14645 ****
  If/when using something like the above, be aware that there are many
  misconfigured systems/mailers out there and so an article's date is not
  always a reliable indication of when it was posted.  Hell, some people
! just don't give a damm.
  
  The above predicates apply to *all* the groups which belong to the
  category.  However, if you wish to have a specific predicate for an
--- 14639,14645 ----
  If/when using something like the above, be aware that there are many
  misconfigured systems/mailers out there and so an article's date is not
  always a reliable indication of when it was posted.  Hell, some people
! just don't give a damn.
  
  The above predicates apply to *all* the groups which belong to the
  category.  However, if you wish to have a specific predicate for an
***************
*** 14750,14756 ****
  @item
  Use @code{normal} score files
  
! If you dont want to maintain two sets of scoring rules for a group, and
  your desired @code{downloading} criteria for a group are the same as your
  @code{reading} criteria then you can tell the agent to refer to your
  @code{normal} score files when deciding what to download.
--- 14750,14756 ----
  @item
  Use @code{normal} score files
  
! If you don't want to maintain two sets of scoring rules for a group, and
  your desired @code{downloading} criteria for a group are the same as your
  @code{reading} criteria then you can tell the agent to refer to your
  @code{normal} score files when deciding what to download.
***************
*** 15038,15045 ****
  
  Gnus keep track of flag changes when reading nnimap groups under the
  Agent by default.  When you plug back in, by default Gnus will check if
! you have any changed any flags and ask if you wish to synchronize theese
! with the server.  This behaviour is customizable with
  @code{gnus-agent-synchronize-flags}.
  
  @vindex gnus-agent-synchronize-flags
--- 15038,15045 ----
  
  Gnus keep track of flag changes when reading nnimap groups under the
  Agent by default.  When you plug back in, by default Gnus will check if
! you have any changed any flags and ask if you wish to synchronize these
! with the server.  This behavior is customizable with
  @code{gnus-agent-synchronize-flags}.
  
  @vindex gnus-agent-synchronize-flags
***************
*** 16066,16072 ****
  @code{Message-ID} to match on the @code{References} header of the
  article.  If the match is made, the @code{Message-ID} of the article is
  added to the @code{thread} rule.  (Think about it.  I'd recommend two
! aspirins afterwards.)
  
  If you use this scheme, you should set the score file atom @code{mark}
  to something small---like -300, perhaps, to avoid having small random
--- 16066,16072 ----
  @code{Message-ID} to match on the @code{References} header of the
  article.  If the match is made, the @code{Message-ID} of the article is
  added to the @code{thread} rule.  (Think about it.  I'd recommend two
! aspirins afterwords.)
  
  If you use this scheme, you should set the score file atom @code{mark}
  to something small---like -300, perhaps, to avoid having small random
***************
*** 16986,16992 ****
  * Compilation::                How to speed Gnus up.
  * Mode Lines::                 Displaying information in the mode lines.
  * Highlighting and Menus::     Making buffers look all nice and cozy.
! * Buttons::                    Get tendonitis in ten easy steps!
  * Daemons::                    Gnus can do things behind your back.
  * NoCeM::                      How to avoid spam and other fatty foods.
  * Undo::                       Some actions can be undone.
--- 16986,16992 ----
  * Compilation::                How to speed Gnus up.
  * Mode Lines::                 Displaying information in the mode lines.
  * Highlighting and Menus::     Making buffers look all nice and cozy.
! * Buttons::                    Get tendinitis in ten easy steps!
  * Daemons::                    Gnus can do things behind your back.
  * NoCeM::                      How to avoid spam and other fatty foods.
  * Undo::                       Some actions can be undone.
***************
*** 17809,17815 ****
  Right.
  
  @vindex gnus-carpal
! Well, you can make Gnus display bufferfuls of buttons you can click to
  do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
  really.  Tell the chiropractor I sent you.
  
--- 17809,17815 ----
  Right.
  
  @vindex gnus-carpal
! Well, you can make Gnus display buffer fulls of buttons you can click to
  do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
  really.  Tell the chiropractor I sent you.
  
***************
*** 18410,18416 ****
  has only an effect if `gnus-picons-display-where' has value `article'.
  
  If @code{nil}, display the picons in the @code{From} and
! @code{Newsgroups} lines.  This is the defailt.
  
  @item gnus-picons-clear-cache-on-shutdown
  @vindex gnus-picons-clear-cache-on-shutdown
--- 18410,18416 ----
  has only an effect if `gnus-picons-display-where' has value `article'.
  
  If @code{nil}, display the picons in the @code{From} and
! @code{Newsgroups} lines.  This is the default.
  
  @item gnus-picons-clear-cache-on-shutdown
  @vindex gnus-picons-clear-cache-on-shutdown
***************
*** 18622,18628 ****
  put it in your @code{From} header of all your news articles.  (I've
  chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
  @samp{larsi+usenet@@ifi.uio.no} will be a better choice.  Ask your
! sysadm whether your sendmail installation accepts keywords in the local
  part of the mail address.)
  
  @lisp
--- 18622,18628 ----
  put it in your @code{From} header of all your news articles.  (I've
  chosen @samp{larsi@@trym.ifi.uio.no}, but for many addresses on the form
  @samp{larsi+usenet@@ifi.uio.no} will be a better choice.  Ask your
! sysadmin whether your sendmail installation accepts keywords in the local
  part of the mail address.)
  
  @lisp
***************
*** 19129,19135 ****
  introduced may confuse casual users.  New features are frequently
  introduced, fiddled with, and judged to be found wanting, and then
  either discarded or totally rewritten.  People reading the mailing list
! usually keep up with these rapid changes, whille people on the newsgroup
  can't be assumed to do so.
  
  
--- 19129,19135 ----
  introduced may confuse casual users.  New features are frequently
  introduced, fiddled with, and judged to be found wanting, and then
  either discarded or totally rewritten.  People reading the mailing list
! usually keep up with these rapid changes, while people on the newsgroup
  can't be assumed to do so.
  
  
***************
*** 23459,23461 ****
--- 23459,23466 ----
  @end iftex
  
  @c End:
+ % LocalWords:  Backend BNF mucho Backends backends detailmenu cindex kindex kbd
+ % LocalWords:  findex Gnusae vindex dfn dfn samp nntp setq nnspool nntpserver
+ % LocalWords:  nnmbox backend newusers Blllrph NEWGROUPS dingnusdingnusdingnus
+ % LocalWords:  pre fab rec comp nnslashdot regex ga ga sci nnml nnbabyl nnmh
+ % LocalWords:  nnfolder emph looong eld newsreaders defun init elc pxref

[-- Attachment #3: Type: text/plain, Size: 57 bytes --]


-- 
Mike Pullen
http://www.midwest.net/scribers/mpullen

Re: Spelling corrections to gnus manual

[ShengHuo ZHU]

Mike Pullen <mpullen@midwest.net> writes:

> Someone please commit these spelling corrections to the gnus manual.

Committed. 


ShengHuo

Re: Spelling corrections to gnus manual

[John H. Palmieri]

ShengHuo ZHU <zsh@cs.rochester.edu> writes:

> Mike Pullen <mpullen@midwest.net> writes:
> 
> > Someone please commit these spelling corrections to the gnus manual.
> 
> Committed. 

Oh dear, I hope you didn't commit them all.  I disagree with these
two, at least:


***************
*** 16066,16072 ****
  @code{Message-ID} to match on the @code{References} header of the
  article.  If the match is made, the @code{Message-ID} of the article is
  added to the @code{thread} rule.  (Think about it.  I'd recommend two
! aspirins afterwards.)
  
  If you use this scheme, you should set the score file atom @code{mark}
  to something small---like -300, perhaps, to avoid having small random
--- 16066,16072 ----
  @code{Message-ID} to match on the @code{References} header of the
  article.  If the match is made, the @code{Message-ID} of the article is
  added to the @code{thread} rule.  (Think about it.  I'd recommend two
! aspirins afterwords.)
  
  If you use this scheme, you should set the score file atom @code{mark}
  to something small---like -300, perhaps, to avoid having small random
***************


(My disagreement: "afterwords" is a noun, meaning "epilogues", while
"afterwards" is an adverb, meaning "at a later time".  You certainly
want the second of these, not the first.  Actually, "afterwards" is
somewhat colloquial; "afterward" would be better than "afterwards".)


***************
*** 17809,17815 ****
  Right.
  
  @vindex gnus-carpal
! Well, you can make Gnus display bufferfuls of buttons you can click to
  do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
  really.  Tell the chiropractor I sent you.
  
--- 17809,17815 ----
  Right.
  
  @vindex gnus-carpal
! Well, you can make Gnus display buffer fulls of buttons you can click to
  do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
  really.  Tell the chiropractor I sent you.
  
***************


(My disagreement: although "bufferfuls" is not a word, it is a
sensible formation, and it looks better, and is more grammatical, than
"buffer fulls".)


-- 
John H. Palmieri                      
Dept of Mathematics, Box 354350    palmieri@math.washington.edu
University of Washington	   http://www.math.washington.edu/~palmieri/
Seattle, WA 98195-4350

Re: Spelling corrections to gnus manual

[Mike Pullen]

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

palmieri@math.washington.edu (John H. Palmieri) writes:


> Oh dear, I hope you didn't commit them all.  I disagree with these
> two, at least:

[...]

> (My disagreement: "afterwords" is a noun, meaning "epilogues", while
> "afterwards" is an adverb, meaning "at a later time".  You certainly
> want the second of these, not the first.  Actually, "afterwards" is
> somewhat colloquial; "afterward" would be better than "afterwards".)


[...]

> (My disagreement: although "bufferfuls" is not a word, it is a
> sensible formation, and it looks better, and is more grammatical, than
> "buffer fulls".)
> 

The attached diff reverts these two changes to the original spelling.
Please commit.  Thanks.


[-- Attachment #2: diff.out --]
[-- Type: application/octet-stream, Size: 1429 bytes --]

*** gnus.texi.mtp	Wed Jan  3 23:03:46 2001
--- gnus.texi2	Thu Jan  4 19:38:23 2001
***************
*** 16066,16072 ****
  @code{Message-ID} to match on the @code{References} header of the
  article.  If the match is made, the @code{Message-ID} of the article is
  added to the @code{thread} rule.  (Think about it.  I'd recommend two
! aspirins afterwords.)
  
  If you use this scheme, you should set the score file atom @code{mark}
  to something small---like -300, perhaps, to avoid having small random
--- 16066,16072 ----
  @code{Message-ID} to match on the @code{References} header of the
  article.  If the match is made, the @code{Message-ID} of the article is
  added to the @code{thread} rule.  (Think about it.  I'd recommend two
! aspirins afterward.)
  
  If you use this scheme, you should set the score file atom @code{mark}
  to something small---like -300, perhaps, to avoid having small random
***************
*** 17809,17815 ****
  Right.
  
  @vindex gnus-carpal
! Well, you can make Gnus display buffer fulls of buttons you can click to
  do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
  really.  Tell the chiropractor I sent you.
  
--- 17809,17815 ----
  Right.
  
  @vindex gnus-carpal
! Well, you can make Gnus display bufferfulls of buttons you can click to
  do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
  really.  Tell the chiropractor I sent you.
  

[-- Attachment #3: Type: text/plain, Size: 57 bytes --]


-- 
Mike Pullen
http://www.midwest.net/scribers/mpullen

Re: Spelling corrections to gnus manual

[ShengHuo ZHU]

palmieri@math.washington.edu (John H. Palmieri) writes:

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > Mike Pullen <mpullen@midwest.net> writes:
> > 
> > > Someone please commit these spelling corrections to the gnus manual.
> > 
> > Committed. 
> 
> Oh dear, I hope you didn't commit them all.  I disagree with these
> two, at least:

Oops. I've revoked these two changes.

ShengHuo

Re: Spelling corrections to gnus manual

[Jeff Senn]

palmieri@math.washington.edu (John H. Palmieri) writes:
> *** 17809,17815 ****
>   Right.
>   
>   @vindex gnus-carpal
> ! Well, you can make Gnus display bufferfuls of buttons you can click to
>   do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
>   really.  Tell the chiropractor I sent you.
>   
> --- 17809,17815 ----
>   Right.
>   
>   @vindex gnus-carpal
> ! Well, you can make Gnus display buffer fulls of buttons you can click to
>   do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
>   really.  Tell the chiropractor I sent you.
>   
> ***************
>
> (My disagreement: although "bufferfuls" is not a word, it is a
> sensible formation, and it looks better, and is more grammatical, than
> "buffer fulls".)

Or "...display buffers full of buttons..." which has the advantage of
being a "proper" formation of English ;-) [as well as the version probably
intended, barring "cuteness"].

-- 
-Jas

Re: Spelling corrections to gnus manual

[John H. Palmieri]

Jeff Senn <senn@maya.com> writes:

> palmieri@math.washington.edu (John H. Palmieri) writes:
> > *** 17809,17815 ****
> >   Right.
> >   
> >   @vindex gnus-carpal
> > ! Well, you can make Gnus display bufferfuls of buttons you can click to
> >   do anything by setting @code{gnus-carpal} to @code{t}.  Pretty simple,
> >   really.  Tell the chiropractor I sent you.
> >   
> 
> Or "...display buffers full of buttons..." which has the advantage of
> being a "proper" formation of English ;-) [as well as the version probably
> intended, barring "cuteness"].

Well, I think cuteness is important, and it's one of the strengths of
the gnus manual :)

-- 
John H. Palmieri                      
Dept of Mathematics, Box 354350    palmieri@math.washington.edu
University of Washington	   http://www.math.washington.edu/~palmieri/
Seattle, WA 98195-4350

Re: Spelling corrections to gnus manual

[Jeff Senn]

palmieri@math.washington.edu (John H. Palmieri) writes:
> > Or "...display buffers full of buttons..." which has the advantage of
> > being a "proper" formation of English ;-) [as well as the version probably
> > intended, barring "cuteness"].
> 
> Well, I think cuteness is important, and it's one of the strengths of
> the gnus manual :)

*LOL* I conceed the point! :-) 

-- 
-Jas