Ken Geis <kgeis(a)speakeasy.org> wrote:
The RemoveWithValues filter has a minor bug. If you,
for example, enter
14 as the attributeIndex property, the option passed to the filter is
"-C 15" where it should be "-C 14". Of course it's easy to work
but it is still a bug.
It's not really a bug but an inconsistency (in fact it's in all the
filters, and probably other classes as well). Indexes entered via
command-line arguments start from 1, but indexes that occur by setting
object properties directly start from 0 (and this is what happens with
the GUI object configuration). It would indeed be nice to have both
command-line and gui object configuration consistent.