[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH] indent: documentation typos
|
From: |
Nicolas Kaiser |
|
Subject: |
[PATCH] indent: documentation typos |
|
Date: |
Wed, 8 Nov 2006 00:44:21 +0100 |
Some documentation typos.
This patch also includes corrections by Erik Sigra from December
2002, and Antoine Trux from October 2002.
Cheers,
n.
---
ChangeLog | 4 ++--
NEWS | 20 ++++++++++----------
README | 2 +-
doc/indent.html | 24 ++++++++++++------------
doc/indent.info | 28 ++++++++++++++--------------
doc/indent.texinfo | 28 ++++++++++++++--------------
man/indent.1 | 22 +++++++++++-----------
7 files changed, 64 insertions(+), 64 deletions(-)
diff -ur indent-2.2.9.orig/ChangeLog indent-2.2.9/ChangeLog
--- indent-2.2.9.orig/ChangeLog 2002-12-16 17:31:10.000000000 +0100
+++ indent-2.2.9/ChangeLog 2006-11-07 22:49:22.000000000 +0100
@@ -35,7 +35,7 @@
* Added option break-function-decl-args-end
(bfde) to break the function arguments list before the closing
bracket.
* -bdfa now causes a break after the opening bracket and before the
first
- argument so that the first argument and subsequent argments are
indented
+ argument so that the first argument and subsequent arguments are
indented
one indentation step instead of being aligned with the opening
bracket.
2002-08-05 Matthias <address@hidden> and Eric Lloyd <address@hidden>
@@ -81,7 +81,7 @@
* indent.dsp, wildcard.c : improvements for vc++.
2001-12-04 Vladislav Naumov <address@hidden>
- * miscel/Makefile.mingw32 : Some fixes for the the mingw32 compiler's
makefile.
+ * miscel/Makefile.mingw32 : Some fixes for the mingw32 compiler's
makefile.
* miscel/config.h.vc++ : prevent UTIME for mingw32.
2001-11-27 David Ingamells <address@hidden>
diff -ur indent-2.2.9.orig/doc/indent.html indent-2.2.9/doc/indent.html
--- indent-2.2.9.orig/doc/indent.html 2002-12-16 17:32:38.000000000 +0100
+++ indent-2.2.9/doc/indent.html 2006-11-07 22:31:31.000000000 +0100
@@ -596,13 +596,13 @@
statements, comments which follow declarations, comments following
preprocessor directives, and comments which are not preceded by code of
any sort, i.e., they begin the text of the line (although not
-neccessarily in column 1).
+necessarily in column 1).
</P><P>
<CODE>indent</CODE> further distinguishes between comments found outside of
procedures and aggregates, and those found within them. In particular,
comments beginning a line found within a procedure will be indented to
-the column at which code is currently indented. The exception to this a
+the column at which code is currently indented. The exception to this is a
comment beginning in the leftmost column; such a comment is output
at that column.
</P><P>
@@ -933,7 +933,7 @@
<A NAME="IDX97"></A>
<A NAME="IDX98"></A>
<A NAME="IDX99"></A>
-The `<SAMP>-saf</SAMP>' option forces a space between an <CODE>for</CODE>
+The `<SAMP>-saf</SAMP>' option forces a space between a <CODE>for</CODE>
and the following parenthesis. This is the default.
</P><P>
@@ -949,14 +949,14 @@
<A NAME="IDX105"></A>
<A NAME="IDX106"></A>
<A NAME="IDX107"></A>
-The `<SAMP>-saw</SAMP>' option forces a space between an <CODE>while</CODE>
+The `<SAMP>-saw</SAMP>' option forces a space between a <CODE>while</CODE>
and the following parenthesis. This is the default.
</P><P>
<A NAME="IDX108"></A>
<A NAME="IDX109"></A>
-The `<SAMP>-prs</SAMP>' option causes all parentheses to be seperated with
-a space from the what is between them. For example, using `<SAMP>-prs</SAMP>'
+The `<SAMP>-prs</SAMP>' option causes all parentheses to be separated with
+a space from whatever is between them. For example, using `<SAMP>-prs</SAMP>'
results in code like:
</P><P>
@@ -1289,7 +1289,7 @@
possible comments that follow it.
</P><P>
-When lines become longer then the specified line length, GNU
<CODE>indent</CODE>
+When lines become longer than the specified line length, GNU
<CODE>indent</CODE>
tries to break the line at a logical place. This is new as of version 2.1
however and not very intelligent or flexible yet.
</P><P>
@@ -1302,7 +1302,7 @@
<A NAME="IDX159"></A>
<A NAME="IDX160"></A>
<A NAME="IDX161"></A>
-Currently there are two options that allows one to interfere with the
+Currently there are two options that allow one to interfere with the
algorithm that determines where to break a line.
</P><P>
@@ -1677,13 +1677,13 @@
<DT>`<SAMP>-cdw</SAMP>'
<DD><DT>`<SAMP>--cuddle-do-while</SAMP>'
-<DD>Cuddle while of <CODE>do {} while;</CODE> and preceeding
`<SAMP>}</SAMP>'.<BR>
+<DD>Cuddle while of <CODE>do {} while;</CODE> and preceding
`<SAMP>}</SAMP>'.<BR>
See section <A HREF="indent.html#SEC8">1.5 Comments</A>.
<P>
<DT>`<SAMP>-ce</SAMP>'
<DD><DT>`<SAMP>--cuddle-else</SAMP>'
-<DD>Cuddle else and preceeding `<SAMP>}</SAMP>'.<BR>
+<DD>Cuddle else and preceding `<SAMP>}</SAMP>'.<BR>
See section <A HREF="indent.html#SEC8">1.5 Comments</A>.
<P>
@@ -1830,7 +1830,7 @@
<DT>`<SAMP>-nbfda</SAMP>'
<DD><DT>`<SAMP>--dont-break-function-decl-args</SAMP>'
-<DD>Don't put each argument in a function declaration on a seperate line.<BR>
+<DD>Don't put each argument in a function declaration on a separate line.<BR>
See section <A HREF="indent.html#SEC10">1.7 Declarations</A>.
<P>
@@ -2037,7 +2037,7 @@
<DT>`<SAMP>-ss</SAMP>'
<DD><DT>`<SAMP>--space-special-semicolon</SAMP>'
-<DD>On one-line <CODE>for</CODE> and <CODE>while</CODE> statments,
+<DD>On one-line <CODE>for</CODE> and <CODE>while</CODE> statements,
force a blank before the semicolon.<BR>
See section <A HREF="indent.html#SEC9">1.6 Statements</A>.
<P>
diff -ur indent-2.2.9.orig/doc/indent.info indent-2.2.9/doc/indent.info
--- indent-2.2.9.orig/doc/indent.info 2002-12-16 17:32:35.000000000 +0100
+++ indent-2.2.9/doc/indent.info 2006-11-07 22:31:52.000000000 +0100
@@ -385,14 +385,14 @@
statements, comments which follow declarations, comments following
preprocessor directives, and comments which are not preceded by code of
any sort, i.e., they begin the text of the line (although not
-neccessarily in column 1).
+necessarily in column 1).
`indent' further distinguishes between comments found outside of
procedures and aggregates, and those found within them. In particular,
comments beginning a line found within a procedure will be indented to
-the column at which code is currently indented. The exception to this a
-comment beginning in the leftmost column; such a comment is output at
-that column.
+the column at which code is currently indented. The exception to this
+is a comment beginning in the leftmost column; such a comment is output
+at that column.
`indent' attempts to leave "boxed comments" unmodified. The general
idea of such a comment is that it is enclosed in a rectangle or "box"
@@ -606,17 +606,17 @@
`sizeof' and its argument. In some versions, this is known as the
`Bill_Shannon' option.
- The `-saf' option forces a space between an `for' and the following
+ The `-saf' option forces a space between a `for' and the following
parenthesis. This is the default.
The `-sai' option forces a space between an `if' and the following
parenthesis. This is the default.
- The `-saw' option forces a space between an `while' and the
+ The `-saw' option forces a space between a `while' and the
following parenthesis. This is the default.
- The `-prs' option causes all parentheses to be seperated with a
-space from the what is between them. For example, using `-prs' results
+ The `-prs' option causes all parentheses to be separated with a
+space from whatever is between them. For example, using `-prs' results
in code like:
while ( ( e_code - s_code ) < ( dec_ind - 1 ) )
@@ -826,11 +826,11 @@
specify the maximum length of a line of C code, not including possible
comments that follow it.
- When lines become longer then the specified line length, GNU `indent'
+ When lines become longer than the specified line length, GNU `indent'
tries to break the line at a logical place. This is new as of version
2.1 however and not very intelligent or flexible yet.
- Currently there are two options that allows one to interfere with the
+ Currently there are two options that allow one to interfere with the
algorithm that determines where to break a line.
The `-bbo' option causes GNU `indent' to prefer to break long lines
@@ -1089,12 +1089,12 @@
`-cdw'
`--cuddle-do-while'
- Cuddle while of `do {} while;' and preceeding `}'.
+ Cuddle while of `do {} while;' and preceding `}'.
*Note Comments::.
`-ce'
`--cuddle-else'
- Cuddle else and preceeding `}'.
+ Cuddle else and preceding `}'.
*Note Comments::.
`-ciN'
@@ -1217,7 +1217,7 @@
`-nbfda'
`--dont-break-function-decl-args'
- Don't put each argument in a function declaration on a seperate
+ Don't put each argument in a function declaration on a separate
line.
*Note Declarations::.
@@ -1391,7 +1391,7 @@
`-ss'
`--space-special-semicolon'
- On one-line `for' and `while' statments, force a blank before the
+ On one-line `for' and `while' statements, force a blank before the
semicolon.
*Note Statements::.
diff -ur indent-2.2.9.orig/doc/indent.texinfo indent-2.2.9/doc/indent.texinfo
--- indent-2.2.9.orig/doc/indent.texinfo 2002-11-10 22:02:48.000000000
+0100
+++ indent-2.2.9/doc/indent.texinfo 2006-11-07 22:12:40.000000000 +0100
@@ -93,7 +93,7 @@
@end titlepage
@page
address@hidden put the following line in the the file dir in the info directory
address@hidden put the following line in the file dir in the info directory
@c under wherever you have installed emacs (assuming that
@c the info file made from this file is in the file "indent")
@c * indent:(indent). How to change the appearance of a C program.
@@ -574,13 +574,13 @@
statements, comments which follow declarations, comments following
preprocessor directives, and comments which are not preceded by code of
any sort, i.e., they begin the text of the line (although not
-neccessarily in column 1).
+necessarily in column 1).
@command{indent} further distinguishes between comments found outside of
procedures and aggregates, and those found within them. In particular,
comments beginning a line found within a procedure will be indented to
-the column at which code is currently indented. The exception to this a
-comment beginning in the leftmost column; such a comment is output
+the column at which code is currently indented. The exception to this
+is a comment beginning in the leftmost column; such a comment is output
at that column.
@command{indent} attempts to leave @dfn{boxed comments} unmodified. The
@@ -915,7 +915,7 @@
@kindex --space-after-for
@kindex -nsaf
@kindex --no-space-after-for
-The @option{-saf} option forces a space between an @code{for}
+The @option{-saf} option forces a space between a @code{for}
and the following parenthesis. This is the default.
@kindex -sai
@@ -929,13 +929,13 @@
@kindex --space-after-while
@kindex -nsaw
@kindex --no-space-after-while
-The @option{-saw} option forces a space between an @code{while}
+The @option{-saw} option forces a space between a @code{while}
and the following parenthesis. This is the default.
@kindex -prs
@kindex --space-after-parentheses
-The @option{-prs} option causes all parentheses to be seperated with
-a space from the what is between them. For example, using @option{-prs}
+The @option{-prs} option causes all parentheses to be separated with
+a space from whatever is between them. For example, using @option{-prs}
results in code like:
@example
@@ -1262,7 +1262,7 @@
possible to specify the maximum length of a line of C code, not including
possible comments that follow it.
-When lines become longer then the specified line length, GNU @command{indent}
+When lines become longer than the specified line length, GNU @command{indent}
tries to break the line at a logical place. This is new as of version 2.1
however and not very intelligent or flexible yet.
@@ -1274,7 +1274,7 @@
@kindex --honour-newlines
@kindex -nhnl
@kindex --ignore-newlines
-Currently there are two options that allows one to interfere with the
+Currently there are two options that allow one to interfere with the
algorithm that determines where to break a line.
The @option{-bbo} option causes GNU @command{indent} to prefer to break
@@ -1560,12 +1560,12 @@
@item -cdw
@itemx --cuddle-do-while
-Cuddle while of @code{do @address@hidden while;} and preceeding
@address@hidden@*
+Cuddle while of @code{do @address@hidden while;} and preceding
@address@hidden@*
@xref{Comments}.
@item -ce
@itemx --cuddle-else
-Cuddle else and preceeding @address@hidden@*
+Cuddle else and preceding @address@hidden@*
@xref{Comments}.
@item address@hidden
@@ -1696,7 +1696,7 @@
@item -nbfda
@itemx --dont-break-function-decl-args
-Don't put each argument in a function declaration on a seperate address@hidden
+Don't put each argument in a function declaration on a separate address@hidden
@xref{Declarations}.
@item -ncdb
@@ -1869,7 +1869,7 @@
@item -ss
@itemx --space-special-semicolon
-On one-line @code{for} and @code{while} statments,
+On one-line @code{for} and @code{while} statements,
force a blank before the address@hidden
@xref{Statements}.
diff -ur indent-2.2.9.orig/man/indent.1 indent-2.2.9/man/indent.1
--- indent-2.2.9.orig/man/indent.1 2002-12-16 17:37:50.000000000 +0100
+++ indent-2.2.9/man/indent.1 2006-11-07 22:32:19.000000000 +0100
@@ -103,12 +103,12 @@
See \fB\ COMMENTS\fR.
.TP
.B -cdw\fR, \fB--cuddle-do-while\fR
-Cuddle while of \fBdo {} while;\fR and preceeding \`}\'.
+Cuddle while of \fBdo {} while;\fR and preceding \`}\'.
.br
See \fB\ COMMENTS\fR.
.TP
.B -ce\fR, \fB--cuddle-else\fR
-Cuddle else and preceeding \`}\'.
+Cuddle else and preceding \`}\'.
.br
See \fB\ COMMENTS\fR.
.TP
@@ -231,7 +231,7 @@
See \fB\ DECLARATIONS\fR.
.TP
.B -nbfda\fR, \fB--dont-break-function-decl-args\fR
-Don\'t put each argument in a function declaration on a seperate line.
+Don\'t put each argument in a function declaration on a separate line.
.br
See \fB\ DECLARATIONS\fR.
.TP
@@ -400,7 +400,7 @@
See \fB\ BLANK\ LINES\fR.
.TP
.B -ss\fR, \fB--space-special-semicolon\fR
-On one-line \fBfor\fR and \fBwhile\fR statments,
+On one-line \fBfor\fR and \fBwhile\fR statements,
force a blank before the semicolon.
.br
See \fB\ STATEMENTS\fR.
@@ -806,13 +806,13 @@
statements, comments which follow declarations, comments following
preprocessor directives, and comments which are not preceded by code of
any sort, i.e., they begin the text of the line (although not
-neccessarily in column 1).
+necessarily in column 1).
.B indent\fR further distinguishes between comments found outside of
procedures and aggregates, and those found within them. In particular,
comments beginning a line found within a procedure will be indented to
-the column at which code is currently indented. The exception to this a
-comment beginning in the leftmost column; such a comment is output
+the column at which code is currently indented. The exception to this
+is a comment beginning in the leftmost column; such a comment is output
at that column.
.B indent\fR attempts to leave \fIboxed comments\fR unmodified. The
@@ -1112,8 +1112,8 @@
The \`-saw\' option forces a space between an \fBwhile\fR
and the following parenthesis. This is the default.
-The \`-prs\' option causes all parentheses to be seperated with
-a space from the what is between them. For example, using \`-prs\'
+The \`-prs\' option causes all parentheses to be separated with
+a space from whatever is between them. For example, using \`-prs\'
results in code like:
.in +5
@@ -1427,11 +1427,11 @@
possible to specify the maximum length of a line of C code, not including
possible comments that follow it.
-When lines become longer then the specified line length, GNU \fBindent\fR
+When lines become longer than the specified line length, GNU \fBindent\fR
tries to break the line at a logical place. This is new as of version 2.1
however and not very intelligent or flexible yet.
-Currently there are two options that allows one to interfere with the
+Currently there are two options that allow one to interfere with the
algorithm that determines where to break a line.
The \`-bbo\' option causes GNU \fBindent\fR to prefer to break
diff -ur indent-2.2.9.orig/NEWS indent-2.2.9/NEWS
--- indent-2.2.9.orig/NEWS 2002-12-12 18:33:37.000000000 +0100
+++ indent-2.2.9/NEWS 2006-11-07 22:14:20.000000000 +0100
@@ -11,7 +11,7 @@
* D.Ingamells <address@hidden> Added option break-function-decl-args-end
(bfde) to break the function arguments list before the closing bracket.
-bdfa now causes a break after the opening bracket and before the first
- argument so that the first argument and subsequent argments are indented
+ argument so that the first argument and subsequent arguments are indented
one indentation step instead of being aligned with the opening bracket.
Release notes for GNU indent version 2.2.8, March 2002
@@ -40,7 +40,7 @@
* New option --break-function-decl-args (-bfda).
This causes each argument of a function declaration to be put on
- a seperate line, aligned with the opening parathesis of the function.
+ a separate line, aligned with the opening parathesis of the function.
For example,
void
@@ -113,10 +113,10 @@
cases (when using the --blank-lines-after-declarations (-bad)).
* A backslash-newline, outside a macro definition or string, was treated
- as two seperate characters, breaking compilation when the newline was
+ as two separate characters, breaking compilation when the newline was
repositioned. Now the backslash is simply eaten.
-Release notes for GNU indent version 2.2.5, Januari 2000
+Release notes for GNU indent version 2.2.5, January 2000
* When using --dont-break-procedure-type, indent wrongly joined
lines of a procedure declaration ending in a '(' and followed
@@ -230,7 +230,7 @@
Release notes for GNU indent version 2.2.0, July 1999
-* Indent was detecting `const' errornous as function qualifier
+* Indent was detecting `const' erroneously as function qualifier
in some cases. Resulting in
void foo(fmt)
@@ -253,7 +253,7 @@
* GNU indent is now a lot more precise in honouring the --line-lengthN
option: It now joins lines when they fit on one line, and it won't
- produce lines that are longer then the specified line length anymore
+ produce lines that are longer than the specified line length anymore
(except when no reasonable break point was found).
* Two new options to accommodate breaking long lines:
@@ -330,10 +330,10 @@
1 : This means `indent' was incorrectly invoked.
2 : Errors occurred during formatting, but processing continued.
- 3 : An unrecoverable error occured during the processing of an input
+ 3 : An unrecoverable error occurred during the processing of an input
file. If there are more input files, indent will proceed to
process them, but will return the error value 3.
- 4 : A serious internal error occured. All processing is terminated.
+ 4 : A serious internal error occurred. All processing is terminated.
5 : A system error during processing occurred. In this case,
`indent' terminates.
@@ -440,7 +440,7 @@
* All reported bugs have been fixed.
* The makefiles have been, hopefully, improved (see the file `README'
- for installation procedure). Essentially, it is sufficent to type
+ for installation procedure). Essentially, it is sufficient to type
"make" to build indent. `indent' is distributed with `configure'
just as other GNU software. Thus, in conformance with the GNU
standards, "configure; make" should function properly and `indent'
@@ -586,7 +586,7 @@
* Only one indent profile is read. indent searches first for a
profile in the current directory and reads that if found.
- Otherwise, indent looks for a profil in the home directory.
+ Otherwise, indent looks for a profile in the home directory.
* "-nip" is now handled. This is equivalent to "-ip0".
diff -ur indent-2.2.9.orig/README indent-2.2.9/README
--- indent-2.2.9.orig/README 2002-12-17 18:33:10.000000000 +0100
+++ indent-2.2.9/README 2006-11-07 20:26:46.000000000 +0100
@@ -70,7 +70,7 @@
How to report bugs:
Please begin your bug report with a concise and factual description
- of the behaviour you consider to be abberant. If you have narrowed
+ of the behaviour you consider to be aberrant. If you have narrowed
the problem down to the use of a particular option, please mention
that. In general, also be sure to mention the command line options
used to invoke indent, as well as the contents of your .indent.pro
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH] indent: documentation typos,
Nicolas Kaiser <=