Re: [PATCH] _git: Add completion for help subcommand

[Bart Schaefer <schaefer@brasslantern.com>]

On Aug 26,  9:55am, Nikolai Weibull wrote:
} Subject: Re: [PATCH] _git: Add completion for help subcommand
}
} On Thu, Aug 26, 2010 at 05:29, Benjamin R. Haskell <zsh@benizi.com> wrote:
} > On Thu, 26 Aug 2010, Nikolai Weibull wrote:
} >
} >> On Sat, Aug 21, 2010 at 14:21, Aaron Schrab wrote:
} >>
} >> Seems fine except for this:
} >>
} >> > +  local formats='(--info -i --man -m --web -w)'
} >>
} >> Although this is sort of nice it doesn't follow the style of this or
} >> other completion files, so please write out the whole list in each
} >> line.
} 
} > It's just visual clutter.  Is there a particular reason not to use a
} > variable?
} 
} Perhaps. The common pattern I saw when I began writing completion
} functions was
}
} (    --b --c)--a
} (--a     --c)--b
} (--a --b    )--c
} 
} I'd really appreciate some kind of vote or input on this.  If we
} decide on using variables they should be used throughout.
}-- End of excerpt from Nikolai Weibull


Nikolai, I think you're missing the point of the abc example you quoted.

In that example, every set inside the parens is different, and the writer
of the function chose to lay them out so that it was obvious where the
differences were.

In the cases that use variables, the subset represented by the variable
is identical in every instance, so it makes sense to write out that
subset only once in the variable assignment.

E.g., both styles are consistent and they could even be mixed:

  def=(--d --e --f)
  (    --b --c $def --g)--a
  (--a     --c $def --g)--b
  (--a --b     $def --g)--c
  (--a --b --c $def    )--g

There's no reason to pick one or the other and require it everywhere.