William Hubbs posted on Fri, 05 Jun 2015 14:12:51 -0500 as excerpted:
On Fri, Jun 05, 2015 at 09:34:42AM -0500, William Hubbs wrote:
On Fri, Jun 05, 2015 at 12:54:45AM -0400, Mike Frysinger wrote:
On 04 Jun 2015 14:10, William Hubbs wrote:
# @DESCRIPTION:
# This eclass is written to ease the
Dnia 2015-06-06, o godz. 09:26:08
Justin Lecher (jlec) j...@gentoo.org napisał(a):
Can we get an agreement on how we are indenting metadata.xml?
I like to properly format and indent metadata.xml, but without having
an agreement or policy on the indention, I make unhappy by choosing
the
On Sat, 06 Jun 2015, Justin Lecher (jlec) wrote:
* 2 spaces
* single tab
So what should it be?
Tabs are too wasteful on space. Therefore, two spaces, and no
indentation of the top-level elements.
Ulrich
pgpmxfmE7_yBp.pgp
Description: PGP signature
On Sat, Jun 06, 2015 at 10:02:53AM +0200, Ulrich Mueller wrote:
On Sat, 6 Jun 2015, Michał Górny wrote:
Tabs are too wasteful on space. Therefore, two spaces, and no
indentation of the top-level elements.
That's nonsense. Tab = 1 byte. Two spaces = 2 bytes.
Visual space.
:set ts=2
Dnia 2015-06-06, o godz. 10:02:53
Ulrich Mueller u...@gentoo.org napisał(a):
On Sat, 6 Jun 2015, Michał Górny wrote:
Tabs are too wasteful on space. Therefore, two spaces, and no
indentation of the top-level elements.
That's nonsense. Tab = 1 byte. Two spaces = 2 bytes.
Visual
Dnia 2015-06-06, o godz. 09:46:27
Ulrich Mueller u...@gentoo.org napisał(a):
On Sat, 06 Jun 2015, Justin Lecher (jlec) wrote:
* 2 spaces
* single tab
So what should it be?
Tabs are too wasteful on space. Therefore, two spaces, and no
indentation of the top-level elements.
That's
On 06/06/15 09:26, Justin Lecher (jlec) wrote:
Hi everyone,
Can we get an agreement on how we are indenting metadata.xml?
I like to properly format and indent metadata.xml, but without having
an agreement or policy on the indention, I make unhappy by choosing
the wrong.
The two options
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi everyone,
Can we get an agreement on how we are indenting metadata.xml?
I like to properly format and indent metadata.xml, but without having
an agreement or policy on the indention, I make unhappy by choosing
the wrong.
The two options which
On Sat, 6 Jun 2015, Michał Górny wrote:
Tabs are too wasteful on space. Therefore, two spaces, and no
indentation of the top-level elements.
That's nonsense. Tab = 1 byte. Two spaces = 2 bytes.
Visual space.
Ulrich
pgpYsZj5GseK_.pgp
Description: PGP signature
On Sat, Jun 06, 2015 at 09:34:41AM +0200, Michał Górny wrote:
Dnia 2015-06-06, o godz. 09:26:08
Justin Lecher (jlec) j...@gentoo.org napisał(a):
Can we get an agreement on how we are indenting metadata.xml?
I like to properly format and indent metadata.xml, but without having
an
On Sat, 6 Jun 2015, Duncan wrote:
*If* we should agree on using tabs, then we should also standardise
the tab width. Using the same rules for indenting and whitespace as
for ebuilds (i.e., tab stops every four positions) suggests itself:
On Sat, 6 Jun 2015, Michał Górny wrote:
Visual space is what you set in your editor. Which also gives tab
the advantage that you can set it to something good for you, like
'more than 2 spaces so that it is readable'.
*If* we should agree on using tabs, then we should also standardise
the tab
On 7 June 2015 at 00:22, Justin Lecher (jlec) j...@gentoo.org wrote:
* linewidth 80 (why do we have this short limit still in 2015)
I wouldn't say this is the reason... but there's a specific benefit for me
at least with the font size I use and the screen size I have.
Means you can fit 2
Ulrich Mueller posted on Sat, 06 Jun 2015 12:17:25 +0200 as excerpted:
On Sat, 6 Jun 2015, Michał Górny wrote:
Visual space is what you set in your editor. Which also gives tab the
advantage that you can set it to something good for you, like 'more
than 2 spaces so that it is readable'.
On Sat, 06 Jun 2015 09:25:33 +0200
Patrick Lauer patr...@gentoo.org wrote:
On 06/06/15 09:26, Justin Lecher (jlec) wrote:
Hi everyone,
Can we get an agreement on how we are indenting metadata.xml?
I like to properly format and indent metadata.xml, but without
having an agreement or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/06/15 14:07, Ulrich Mueller wrote:
On Sat, 6 Jun 2015, Duncan wrote:
*If* we should agree on using tabs, then we should also
standardise the tab width. Using the same rules for indenting
and whitespace as for ebuilds (i.e., tab stops
* linewidth 80 (why do we have this short limit still in 2015)
Actually, I dislike that too, but the reason is simple: some people still
using text-mode terminals.
// It would be nice to finally fix that, but let's be realistic: it looks like
it wouldn't be finished in the near 10 years :-/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/06/15 17:21, Michael Orlitzky wrote:
On 06/06/2015 08:22 AM, Justin Lecher (jlec) wrote:
* linewidth 80 (why do we have this short limit still in
2015)
It's ancient typographic wisdom that the optimal measure (number of
characters
On 06/06/2015 08:22 AM, Justin Lecher (jlec) wrote:
* linewidth 80 (why do we have this short limit still in 2015)
It's ancient typographic wisdom that the optimal measure (number of
characters in column of text) is somewhere between 45 and 75. It varies
somewhat depending on the typeface
Hi,
the list of packages that I'm no longer interested in:
media-sound/apulse -- needs version bump
dev-util/android-ndk -- needs version bump
I will remove myself from maintainers of these packages and, if there is
no other maintainers reassign bugs to maintainer-needed.
dev-util/ext4_utils
On Sat, Jun 06, 2015 at 06:02:48PM +0200, Jauhien Piatlicki wrote:
Hi,
the list of packages that I'm no longer interested in:
media-sound/apulse -- needs version bump
dev-util/android-ndk -- needs version bump
I'll take android-ndk since I already maintain android-studio.
-- Jason
Am Samstag, 6. Juni 2015, 09:26:08 schrieb Justin Lecher (jlec):
Hi everyone,
Can we get an agreement on how we are indenting metadata.xml?
I like to properly format and indent metadata.xml, but without having
an agreement or policy on the indention, I make unhappy by choosing
the wrong.
On Sat, Jun 6, 2015 at 3:26 AM, Justin Lecher (jlec) j...@gentoo.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi everyone,
Can we get an agreement on how we are indenting metadata.xml?
I like to properly format and indent metadata.xml, but without having
an agreement or
Andrew Savchenko posted on Sat, 06 Jun 2015 20:36:13 +0300 as excerpted:
On Sat, 06 Jun 2015 18:35:41 +0600 Vadim A. Misbakh-Soloviov wrote:
* linewidth 80 (why do we have this short limit still in 2015)
Actually, I dislike that too, but the reason is simple: some people
still using
On Sat, 06 Jun 2015 18:35:41 +0600 Vadim A. Misbakh-Soloviov wrote:
* linewidth 80 (why do we have this short limit still in 2015)
Actually, I dislike that too, but the reason is simple: some people still
using text-mode terminals.
// It would be nice to finally fix that, but let's be
The two options which are already suggested are
* 2 spaces
* single tab
So what should it be?
Two spaces per indention with a maximum line width of 80 single-width
Unicode grapheme clusters (equals the with of 80 ASCII characters).
--
Allan Wegan
Jabber: allanwe...@jabber.ccc.de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/06/2015 09:02 AM, Jauhien Piatlicki wrote:
Hi,
the list of packages that I'm no longer interested in:
media-sound/apulse -- needs version bump dev-util/android-ndk --
needs version bump
I will remove myself from maintainers of these
On Sat, 06 Jun 2015 14:22:38 +0200 Justin Lecher (jlec) wrote:
Exactly, that was my intention.
How about
* indent with tab
* tab == 4 spaces
* linewidth 80 (why do we have this short limit still in 2015)
Because of readability and ergonomics. The optimal page width is
about 67
28 matches
Mail list logo
