Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 2892] TShark has no way to include the summary "Info" column in fields output

[bugzilla-daemon@xxxxxxxxxxxxx]

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2892

Michael Mann <mmann78@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #9571|                            |review_for_checkin?
              Flags|                            |

--- Comment #4 from Michael Mann <mmann78@xxxxxxxxxxxx> 2012-11-24 09:41:41 PST ---
Created attachment 9571
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=9571
Bare bones functionality of "Info" column as field

This is a barebones patch that allows the "Info" column as a field.  In fact it
allows any column to be considered a field as long as the "col." prefix is
used.  I wanted some comments before committing, especially to make sure I
didn't cross some "architectural" boundaries when "merging" column and
"dissector filter" data.

Some things that are missing/incomplete (feel free to add to the list)
1. Help documentation updates
2a. Should "col" be used as a "filter prefix" for columns?  It made the logic
much more "efficient" to have a known prefix for columns rather than going
strictly with the column name (and probably always processing the column data,
whether its listed as a field or not)
2b. Should "col" be registered somewhere as a "reserved" name, so we don't have
a dissector with "col" as the PROTOABBREV?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.