Junio C Hamano wrote:
> Jakub Narebski <jnareb@xxxxxxxxx> writes:
>
>> Code should be aligned the same way, regardless of tab size.
>> Use tabs for indent, but spaces for align.
>
> I do not necessarily agree with that policy; the result of
> applying this patch is still inconsistent in some places, and I
> think that is primarily because the policy itself is flawed.
To be true I do those "whitespace cleanup" patches when I notice
that something is mis-aligned for _my_ tab width (2 spaces).
I use Emacs with show-whitespace-mode to not introduce errors
which would be aligned for 2 columsn wide tabs but be misaligned
for more common 5 or 8 characters wide tabs.
> For example, a part of sub format_paging_nav looks like this:
>
> sub format_paging_nav {
> >>>>>>>>my ($action, $hash, $head, $page, $nrevs) = @_;
> ...
> >>>>>>>>if ($page > 0) {
> >>>>>>>>>>>>>>>>$paging_nav .= " ⋅ " .
> >>>>>>>>>>>>>>>>>>>>>>>>$cgi->a({-href => href(action=>$a
> >>>>>>>>>>>>>>>>>>>>>>>> -accesskey => "p", -titl
> >>>>>>>>} else {
> ...
>
> If your policy is to indent continuation lines (which is why you
> have a TAB before "$cgi->a"), not having a TAB before the
> continued parameter list for the $cgi->a() call look inconsistent.
>
> If on the other hand your policy is to align parameters to an
> operator that are spread over multiple lines, " ⋅ " and
> "$cgi-a(..." are left and right parameters to the string
> concatenation operator "." in between them, so "$cgi->a" should
> be pushed back with a run of SP starting at the column that
> begins $paging_nav and aligned with the DQ at the beginning of
> the " ⋅ " string.
That is preferred, and usually used policy, although I sometimes
use former to avoid too long lines.
I never claimed to be perfect...
Nevertheless this patch for example correct situation where the
line which should be aligned is aligned using mixture of tabs and
spaces differing from line to line in the "same alignment" block.
--
Jakub Narebski
Poland
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html