From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>,
Eli Zaretskii <eliz@gnu.org>
Subject: [doc] Re: [RFC] s/preceed/precede/
Date: Mon, 04 Jul 2011 20:02:00 -0000 [thread overview]
Message-ID: <1309809372.4471.20.camel@hactar> (raw)
In-Reply-To: <20110704194610.GR2407@adacore.com>
On Mon, 2011-07-04 at 12:46 -0700, Joel Brobecker wrote:
> > It looks like "preceed" is wrong and "precede" is right. I can't find
> > "preceed" in neither Merriam-Webster nor dictionary.com. Also, there are
> > many places using "precede" in GDB's source code.
> >
> > But "preceed" is so common that I'm not so sure about this patch.
> > Perhaps it's just an alternative spelling?
>
> As far as I can tell "preceed" is not correct. In fact, I can see
> pages where this is explicitly listed as a mispelling. For instance,
> the following Wikipedia page:
> http://en.wikipedia.org/wiki/Wikipedia:Lists_of_common_misspellings/For_machines
> And I found evidence that he same fix was made in the ZSH code.
Thanks for the research!
> > 2011-07-04 Thiago Jung Bauermann <bauerman.ibm.com>
> >
> > gdb/
> > * ada-lang.c: Fix typos.
> > * amd64-tdep.c: Likewise.
> > * breakpoint.c: Likewise.
> > * cli/cli-decode.c: Likewise.
> > * findcmd.c: Likewise.
> > * inline-frame.c: Likewise.
> > * mi/mi-main.c: Likewise.
> > * minsyms.c: Likewise.
> > * monitor.c: Likewise.
> > * monitor.h: Likewise.
> > * prologue-value.c: Likewise.
> > * reverse.c: Likewise.
> > * s390-tdep.c: Likewise.
> >
> > gdb/testsuite/
> > * gdb.base/call-sc.c: Likewise.
> > * gdb.base/ifelse.exp: Likewise.
> > * gdb.base/structs.c: Likewise.
> >
> > gdb/doc/
> > * gdb.texinfo: Likewise.
>
> OK.
Great. I forgot to mention that two of these typos are in error
messages. One related to the break-range command:
- error (_("Invalid address range, end preceeds start."));
+ error (_("Invalid address range, end precedes start."));
and the other related to the find command:
- error (_("Invalid search space, end preceeds start."));
+ error (_("Invalid search space, end precedes start."));
Does it matter? I guess not, since we only support parseable output in
the MI.
Also, I forgot to mark in the subject that this touches the
documentation, so I'm copying Eli.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2011-07-04 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 19:38 Thiago Jung Bauermann
2011-07-04 19:49 ` Joel Brobecker
2011-07-04 20:02 ` Thiago Jung Bauermann [this message]
2011-07-04 20:16 ` [doc] " Joel Brobecker
2011-07-05 2:48 ` Eli Zaretskii
2011-07-05 6:27 ` Thiago Jung Bauermann
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=1309809372.4471.20.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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