Comment # 7
on bug 9317
from Chris Maynard
(In reply to comment #6)
> Hmm, I am also confused by that code. Is the frame number in the default
> column format string for tshark, and we use this to hide it by default
> during live capture? In that case perhaps tshark live captures should have
> there own, distinct default column format string instead?
I thought that tshark used Wireshark's column settings, but that doesn't appear
to be the case, although I'm not sure why it doesn't, especially when you have
different columns configured for different profiles. I think it would be much
nicer to be able to more easily control tshark column output by taking
advantage of those already pre-configured column layouts using, e.g., "tshark
-O foo" or "tshark -O bar". Another strange thing I notice is that when you do
specify a profile, such as "tshark -O foo", you get different output than if
you don't specify the profile. Without the profile option, you get the column
data printed, but with the profile option you instead get packet details but no
column data.
Anyway, regarding this bug and patch, I'm guessing that it's an artifact from
the days when if you were writing to a file, you couldn't also display the
packets (and vice versa). Thus, someone didn't think that printing frame
numbers would be useful because you wouldn't have a capture file to later
reference. But even then it doesn't make sense to me because you could have
redirected the output to a file and then it might have been useful to refer to
frame numbers in the text file.
You are receiving this mail because:
- You are watching all bug changes.
