[Nut-upsdev] [PATCH 14/36] Note that if you're going to be strict about use of tabs for indenting for the purpose of allowing viewing at different tab widths then you need to be strict about use of spaces for alignment of text after tabs.
Arnaud Quette
aquette.dev at gmail.com
Mon May 14 08:56:53 UTC 2012
2012/3/9 Greg A. Woods <woods at planix.com>:
> From: "Greg A. Woods" <woods at planix.com>
>
> ---
> docs/developers.txt | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/docs/developers.txt b/docs/developers.txt
> index f26dd17..38708d7 100644
> --- a/docs/developers.txt
> +++ b/docs/developers.txt
> @@ -171,6 +171,11 @@ without inflicting much pain on other developers. If you use a space,
> then you've fixed the spacing in stone and have really annoyed half of
> the people out there.
>
> +Note that tabs apply only to *indenting*. Alignment of text after any
> +non-tab character has appeared on the line must be done by spaces in
> +order for it to remain at the same alignment when someone views tabs at
> +a different widths.
> +
> If you write something that uses spaces, you may get away with it in a
> driver that's relatively secluded. However, if I have to work on that
> code, expect it to get reformatted according to the above.
applied to trunk, r3580.
thanks.
Arnaud
--
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/
More information about the Nut-upsdev
mailing list