zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: zsh workers <zsh-workers@sunsite.dk>
Subject: Re: [PATCH 2/2] Fix typos in completion style guide.
Date: Sun, 12 Oct 2008 10:59:57 +0000	[thread overview]
Message-ID: <20081012105957.GA14857@scru.org> (raw)
In-Reply-To: <alpine.LNX.2.00.0810121123460.15079@localhost>

On Sun, Oct 12, 2008 at 11:24:23AM +0200, Mikael Magnusson wrote:
> ---
>  Etc/completion-style-guide |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Etc/completion-style-guide b/Etc/completion-style-guide

This one broke because of wrapping.  Hand-applied; you can check what
I've missed this time below:

Index: Etc/completion-style-guide
===================================================================
RCS file: /cvsroot/zsh/zsh/Etc/completion-style-guide,v
retrieving revision 1.8
diff -u -r1.8 completion-style-guide
--- Etc/completion-style-guide	23 Jul 2003 11:06:59 -0000	1.8
+++ Etc/completion-style-guide	12 Oct 2008 10:58:14 -0000
@@ -8,7 +8,7 @@
 Coding style:
 
 * Use two spaces for indentation and four for continuation lines except
-  where there are many continutation lines such as `_arguments' or
+  where there are many continuation lines such as `_arguments' or
   `_values' specs. Lines tend to be longer than in C code so less
   indentation makes sense.
 
@@ -46,7 +46,7 @@
 per-match descriptions; they are better placed in the group
 descriptions. Put the units in parentheses after the description. So
 for example, do not use:
-  '--timeout[specifiy connection timeout in milliseconds]:timeout'
+  '--timeout[specify connection timeout in milliseconds]:timeout'
 but use:
   '--timeout[specify connection timeout]:timeout (ms)'
   
@@ -63,7 +63,7 @@
 
 Where two matches have identical meaning, give them the same
 description so that the completion system can group them together.
-Conventionally a brace exapansion of this form is used:
+Conventionally a brace expansion of this form is used:
   '(--context,-C)'{--context=,-C-}'[specify lines of context]:lines'
 You won't need the exclusion list if the option can be specified
 multiple times. It can also be useful to use the same description for


  reply	other threads:[~2008-10-12 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12  9:23 [PATCH 1/2] Fix typos in development guide Mikael Magnusson
2008-10-12  9:24 ` [PATCH 2/2] Fix typos in completion style guide Mikael Magnusson
2008-10-12 10:59   ` Clint Adams [this message]
2008-10-12 11:04     ` Mikael Magnusson

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=20081012105957.GA14857@scru.org \
    --to=clint@zsh.org \
    --cc=mikachu@gmail.com \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).