I hope that you are well.
Thank you very much for your work on this really useful software and
its documentation.
I have some feedback on the manual at:
http://www.gnu.org/software/indent/manual/indent.html
indent looks for .indent.pro in the current directory and use that if
found.
Perhaps change "use" to "uses".
In the case of preprocessor directives,comments are extended to to
one space past the end of the directive.
Perhaps put a space after the comma.
Perhaps change "to to" to "to".
The arguments will appear at one indention level deeper than the
function declaration.
Perhaps change "indention" to "indentation".
The most basic, and most controversial issues with regard to code
formatting is precisely how indentation should be acoomplished.
Perhaps change "issues" to "issue".
Perhaps change "acoomplished" to "accomplished".
Fortunately, indent supports several different styles of identation.
Perhaps change "identation" to "indentation".
The -as option fixes this so that the code will appear consistent
regardless of what tab size the user users to read the code.
Perhaps change "user users" to "user uses".
This option can be used to request that preprocessor conditional
statements can be indented by to given number of spaces,
Perhaps change "by to" to "by a".
The -nbbo option causes GNU indent not have that preference.
Perhaps change "not have" to "not to have".
Comments of the form /*UPPERCASE*/ are not treated as comment but as
an identifier, causing them to be joined with the next line.
Perhaps change "comment but as an identifier" to "comments but as
identifiers" to give:
Comments of the form /*UPPERCASE*/ are not treated as comments but as
identifiers, causing them to be joined with the next line.
Or change "Comments" to "A comment" and change "are" to "is" and change
"as comment" to "as a comment" and change "them" to "it" to give:
A comment of the form /*UPPERCASE*/ is not treated as a comment but
as an identifier, causing it to be joined with the next line.
Thank you.
David
