Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: Re: [Ethereal-dev] Could someone with more knowledge than me update/improve the

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: Ulf Lamping <ulf.lamping@xxxxxx>
Date: Wed, 12 Oct 2005 22:01:31 +0200
Jaap Keuter wrote:

Hi,

It is not so much the -r option that is misleading, it's the synopsys
which doesn't make clear that the command can work on a range of packets.
I can suggest the following change for that:

Index: editcap.pod
===================================================================
--- editcap.pod (revision 16189)
+++ editcap.pod (working copy)
@@ -16,7 +16,7 @@
S<[ B<-v> ]>
I<infile>
I<outfile>
-S<[ I<record#> ... ]>
+S<[ [-I<record#>] | [I<record#>[-[I<record#>]] ] [...]>

=head1 DESCRIPTION

This changes the synopsys into

SYNOPSYS
      editcap [ -E error probability] [ -F file format ] [ -h ] [ -r ]
      [ -s snaplen ] [ -t time adjustment ] [ -T encapsulation type ]
      [ -v ] infile outfile [ [-record#] | [record#[-[record#]] ] [...]

And even though it is more complicated it covers the ranges question.

Thanks for trying to fix this.

IMHO Unfortunately, I think it complicates more than it solves.

Why not simply add an (a few) *examples* of the usage.

Regards, ULFL