On Mon, Sep 01, 2008 at 05:42:42PM +0800, [EMAIL PROTECTED] was heard to say:
> name
> Matches packages whose names match the regular expression name. This
> is
> the “default” search mode and is used for patterns that don't start
> with ~.
>
> Say if these are bounded regexps, with invisible ^ and $ added at the
> ends or not. E.g., dlocate -l and dpkg -l all do it their own way so
> say what aptitude does please.
All aptitude regex matches are against substrings; this is pretty
much standard for programs that search by regex (in fact, I can't
think of any counterexamples). I'm not going to add text stating this
to every pattern that uses a regular expression, but I will add a brief
comment in the place where the documentation mentions that most
searches use regular expressions.
> [Note] Note
> To include a “!” in a regular expression, it must be “escaped” to
> prevent aptitude from considering it part of a NOT term: “~!”.
>
> That is a bit ambiguous. Better might be:
OK, I've rewritten that text to include an example and to define
escaping more directly. I've also included a note on this twist in the
section on searching for strings.
> ?any-version(pattern)
> Matches a package if any one of its versions matches the enclosed
> term.
>
> Here you say pattern, then say term.
I have a bad habit of using "term" and "pattern" interchangeably. In
some fields "term" means any expression -- but aptitude tends to use
"term" to specifically mean the individual parts of an expression, and
mainly just the search terms that have names. I've corrected all the
places I could find where "term" was used as above.
(I could also just use "pattern" or "term" everywhere, but I think the
distinction is useful)
> ?new, ~N
> Matches packages which are new.
>
> OK, but give a link or say what you mean by "new".
Added a note (it's packages added to the archive since the last
"Actions -> Forget New Packages" or "aptitude forget-new".
> And maybe new is a GUI users' thing, which I would hardly brush up
> with as I currently only like the command line.
?new is exactly how you access the list of new packages from the
command-line.
> $ 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.
In fact, *set* is exactly what is intended here: these command-line
options override the configuration setting, whatever it is. There were
several places where the opposite problem existed (saying "is true"
instead of "is set"), and I've fixed those.
(NB: the shell doesn't enter into it; these are apt options)
> 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.
Do I mention apt-config somewhere? I can't find any references.
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
