On Thu, Sep 04, 2008 at 02:46:42AM +0800, [EMAIL PROTECTED] was heard to say:
> >> $ COLUMNS=2222 man aptitude|grep 'even .* is set'|perl -pwe
> >> 's/.*(.{33})/$1/'
> >> Resolver::No-New-Upgrades is set.
> >> Resolver::No-New-Installs is set.
> >> Say is set to what, true or false.
> >> As you know with the shell, unset, set to null, set to something, are
> >> all different.
>
> DB> In fact, *set* is exactly what is intended here: these command-line
> DB> options override the configuration setting, whatever it is. There were
> DB> several places where the opposite problem existed (saying "is true"
> DB> instead of "is set"), and I've fixed those.
>
> OK, but then perhaps say "is set to anything, even ''", else
> unfortunately people will think you still mean "is set to true"!
> (Or maybe say "anything except false", or "not unset")
I think a better wording would be "regardless of the value of <blah>".
> >> P.S.S. In
> >> Title: Configuration file reference
> >> URL: file:///usr/share/doc/aptitude/html/en/ch02s04s05.html
> >> perhaps mention that "apt-config dump" will show all the current
> >> value except those from ~/.aptitude I suppose.
>
> DB> Do I mention apt-config somewhere? I can't find any references.
>
> That's why I'm saying perhaps mention it.
I must be missing the point, then. What does apt-config have to do
with aptitude? Aside from the fact that they're both apt tools. I
don't document how apt-get works, or how wajig works, or how synaptic
works, or how firefox works, because this is documentation for aptitude.
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
