On 2006/02/19 06:02, Roland Illig wrote:
> Mark E. Perkins wrote:
> 
>> Even better, IMO, would be to use the same leader everywhere, but to
>> have the text for the steps indented more than the text for the stages
>> (the additional white space helps even more to set things apart
>> visually, which is part of what I think you are trying to accomplish):
>>
>> => Checking for vulnerabilities in pkglint-4.57
>> => Extracting for pkglint-4.57
>> =>   Required installed package digest>=20010101: digest-20050731 found
>> =>   Required installed package perl>=5.0: perl-5.8.7nb8 found
>> => Patching for pkglint-4.57
>> => Overriding tools for pkglint-4.57
>> => Configuring for pkglint-4.57
>> =>   Setting compile-time constants for pkglint.
>> => Installing for pkglint-4.57
>> =>   Creating installation directories
>> =>   [Automatic manual page handling]
>> =>   Registering installation for pkglint-4.57
>> =>     Checking for work-directory references in pkglint-4.57
>> => Checking for non-existent script interpreters in pkglint-4.57
>> => Packaging pkglint-4.57
>> =>   Building binary package for pkglint-4.57
>>
>> or use the '===>' leader everywhere.
> 
> 
> This looks really cute. Maybe we should make this layout the default.
> And if someone doesn't like this style (or should I say theme), {s,}he
> can configure it to something else.
> 
> .oO(pkgsrc themes)

Cuteness was not a consideration. ;) Reducing visual clutter with a bit of white
space and, thereby, improving readability was.

Whether the choice of leader is a pkgsrc configuration option is something
probably not worth much effort, IMO.

Mark