Bug ID |
10085
|
Summary |
Synonymous "contains" operator for display filters
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.6
|
Hardware |
x86
|
OS |
Mac OS X 10.9
|
Status |
UNCONFIRMED
|
Severity |
Enhancement
|
Priority |
Low
|
Component |
Wireshark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
Version 1.10.6 (v1.10.6 from master-1.10)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.17, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.36.0, with libpcap, with libz 1.2.3, without POSIX capabilities, without
libnl, with SMI 0.4.8, without c-ares, without ADNS, with Lua 5.1, without
Python, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP,
with PortAudio V19-devel (built Jul 16 2013 19:05:52), with AirPcap.
Running on Mac OS X 10.9.2, build 13C64 (Darwin 13.1.0), with locale .UTF-8,
with libpcap version 1.3.0 - Apple version 41, with libz 1.2.5, GnuTLS 2.12.19,
Gcrypt 1.5.0, without AirPcap.
Intel(R) Core(TM)2 Duo CPU P7550 @ 2.26GHz
Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
2336.9.00).
--
For more legible display filter notations, consider adding a shorthand for
"contains" and "matches" operator.
E.g. "*=" or "?=" (made-up)
Turning
sip contains 12345 or sip matches "(?i)cldc"
into
sip*=12345 or sip?="(?i)cldc"
Reducing the alphabetic characters makes display filters shorter (fitting more
information in the confined space of the display filter field) and easier to
parse for the human eye.
Also, making those synonymous with the existing operators, their shouldn't be
side effects for existing users.
You are receiving this mail because:
- You are watching all bug changes.