public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Berntsen <bernalex@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Indentation level
Date: Wed, 26 Mar 2014 12:04:11 +0100	[thread overview]
Message-ID: <5332B42B.9020905@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Alignment is a PITA with hard tabs, so can we at least agree on what
tab stop to use? I naïvely mentioned in DEVELOPING that it should be
set to 4, because that's what every Python standard uses. But
throughout the code it varies.

There are plenty of examples of stuff that's aligned using tabs, see
UseManager's init comment for an example. Notice how it is obviously
formatted by somebody using 8 as their tab stop. People who have set
their tab stop to the Python standard will just see an ugly mess.

It's not a big issue, but if we can agree on a rule, I can add it to
the DEVELOPING, and people can just change stuff that assumes a wrong
tab stop.

To avoid bikeshedding I just propose to set it to 4. Any objections?
- -- 
Alexander
bernalex@gentoo.org
https://secure.plaimi.net/~alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlMytCsACgkQRtClrXBQc7WYKwD+O8RBe5WJIDv6vmonPieJwiI/
AfJLP3ihJswJNaQo1UgA/iJKrhTZ2Qq2h6gEnYvhmuD6FBCmI2ynukk51iuzmi3E
=BXE9
-----END PGP SIGNATURE-----


             reply	other threads:[~2014-03-26 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-26 11:04 Alexander Berntsen [this message]
2014-03-26 12:23 ` [gentoo-portage-dev] Indentation level Tom Wijsman
2014-03-26 12:26   ` Alexander Berntsen
2014-03-28  8:50 ` [gentoo-portage-dev] [PATCH] DEVELOPING: Be more specific about tabs/spaces Alexander Berntsen

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=5332B42B.9020905@gentoo.org \
    --to=bernalex@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox