coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 1/2] doc: fix spacing


From: Jim Meyering
Subject: Re: [PATCH 1/2] doc: fix spacing
Date: Thu, 12 Jul 2012 10:53:05 +0200

Paul Eggert wrote:
> * doc/coreutils.texi: Use right amount of spacing after punctuation.
> ---
>  doc/coreutils.texi |  159 
> ++++++++++++++++++++++++++--------------------------
>  1 files changed, 80 insertions(+), 79 deletions(-)
>
> diff --git a/doc/coreutils.texi b/doc/coreutils.texi
> index 954a1f8..3c7f4e5 100644
> --- a/doc/coreutils.texi
> +++ b/doc/coreutils.texi
> @@ -585,7 +585,7 @@ symbolic link to a directory.  @xref{Target directory}.
>  @opindex --null
>  @cindex output @sc{nul}-byte-terminated lines
>  Output a zero byte (@acronym{ASCII} @sc{nul}) at the end of each line,
> -rather than a newline. This option enables other programs to parse the
> +rather than a newline.  This option enables other programs to parse the
>  output of @command{\cmd\} even when that output would contain data
>  with embedded newlines.
>  @end macro
> @@ -1046,7 +1046,7 @@ floating point numbers such as @code{-0x.ep-3},
> which stands for
>  A @var{signal} may be a signal name like @samp{HUP}, or a signal
>  number like @samp{1}, or an exit status of a process terminated by the
>  signal.  A signal name can be given in canonical form or prefixed by
> address@hidden  The case of the letters is ignored. The following signal names
> address@hidden@.  The case of the letters is ignored.  The following signal 
> names
>  and numbers are supported on all @acronym{POSIX} compliant systems:

Thanks!  This looks like something we could automate a check for,
otherwise I'll surely forget and introduce new instances.
Do you know of tools to help with that?

I'd say grep, but we'd need more context to filter out false positives.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]