| 1 |
Ulrich Mueller posted on Sat, 06 Jun 2015 12:17:25 +0200 as excerpted: |
| 2 |
|
| 3 |
>>>>>> On Sat, 6 Jun 2015, Michał Górny wrote: |
| 4 |
> |
| 5 |
>> Visual space is what you set in your editor. Which also gives tab the |
| 6 |
>> advantage that you can set it to something good for you, like 'more |
| 7 |
>> than 2 spaces so that it is readable'. |
| 8 |
> |
| 9 |
> *If* we should agree on using tabs, then we should also standardise the |
| 10 |
> tab width. Using the same rules for indenting and whitespace as for |
| 11 |
> ebuilds (i.e., tab stops every four positions) suggests itself: |
| 12 |
> https://devmanual.gentoo.org/ebuild-writing/file-format/ |
| 13 |
index.html#indenting-and-whitespace |
| 14 |
|
| 15 |
The bike shed simply /must/ be black... with pink polka dots! =:^) |
| 16 |
|
| 17 |
(Somewhat) More seriously, standardizing the tab size defeats the |
| 18 |
purpose, letting people decide for themselves, particularly when it's to |
| 19 |
be the declared horizontal spacing standard in a file such as this, where |
| 20 |
mixed spaces and tabs can be avoided, so someone's personal setting |
| 21 |
shouldn't be mixed up by someone using spaces instead (and if it is, the |
| 22 |
non-standard spaces in place of tabs is simply much more obvious, |
| 23 |
allowing easier detection /due/ to the non-standardized tabsize, and |
| 24 |
replacing with tabs as appropriate). |
| 25 |
|
| 26 |
But IMO it's all simply bikeshedding, regardless. |
| 27 |
|
| 28 |
-- |
| 29 |
Duncan - List replies preferred. No HTML msgs. |
| 30 |
"Every nonfree program has a lord, a master -- |
| 31 |
and if you use the program, he is your master." Richard Stallman |
Archives