Gnus development mailing list
 help / color / mirror / Atom feed
From: Jeff Senn <senn@maya.com>
Subject: Re: Spelling corrections to gnus manual
Date: 09 Jan 2001 09:07:14 -0500	[thread overview]
Message-ID: <n1d0zunh.fsf@SNIPE.maya.com> (raw)
In-Reply-To: <s5tu27dekrx.fsf@goedel2.math.washington.edu>


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




      reply	other threads:[~2001-01-09 14:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04  5:10 Mike Pullen
2001-01-04  6:54 ` ShengHuo ZHU
2001-01-04 19:09   ` John H. Palmieri
2001-01-05  1:42     ` Mike Pullen
2001-01-05  5:28     ` ShengHuo ZHU
2001-01-05 17:06     ` Jeff Senn
2001-01-05 21:44       ` John H. Palmieri
2001-01-09 14:07         ` Jeff Senn [this message]

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=n1d0zunh.fsf@SNIPE.maya.com \
    --to=senn@maya.com \
    /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;
as well as URLs for NNTP newsgroup(s).