Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: dj@redhat.com, gcc@gcc.gnu.org, binutils@sources.redhat.com,
	gdb@sources.redhat.com
Subject: Re: libiberty docs are in
Date: Thu, 27 Sep 2001 12:01:00 -0000	[thread overview]
Message-ID: <20010927150200.G6776@disaster.jaj.com> (raw)
In-Reply-To: <1659-Thu27Sep2001121904+0300-eliz@is.elta.co.il>

On Thu, Sep 27, 2001 at 12:19:05PM +0200, Eli Zaretskii wrote:
> [Repeat after me: "it's ``occurrence'', not ``occurance'' ;-)  May I
> suggest "M-x ispell-comments-and-strings RET"?]

Certainly you may, but it won't cause me to start using Emacs...

I take responsibilty for the original state of comments, and I wasn't
about to try and run a texinfo file through any of the spell checkers I had
available to me at the time.  There used to be a DVI-to-plaintext converter
for just this sort of situation, but it never worked quite right and seems
to have become unsupported since the last time I used it.

The solution, of course, is for me to learn how to spell.  :-)

Thanks for the fixes,
Phil

-- 
"You have to wonder what kind of life you have when your list of personal
rules begins with, '#3:  No drowning in your own mucus,' and '#4:  Don't
ask what happened to rules 1 and 2.'"


  parent reply	other threads:[~2001-09-27 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 11:56 DJ Delorie
2001-09-27  3:20 ` Eli Zaretskii
     [not found] ` <1659-Thu27Sep2001121904+0300-eliz@is.elta.co.il>
2001-09-27  9:57   ` DJ Delorie
2001-09-27 12:07     ` Eli Zaretskii
     [not found]     ` <3099-Thu27Sep2001205015+0300-eliz@is.elta.co.il>
2001-09-27 12:58       ` DJ Delorie
2001-09-27 12:01   ` Phil Edwards [this message]
2001-09-27 13:12     ` DJ Delorie
2001-09-27 13:15       ` Phil Edwards
2001-09-27 13:54     ` Eli Zaretskii

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=20010927150200.G6776@disaster.jaj.com \
    --to=pedwards@disaster.jaj.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.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