Wireshark-bugs: [Wireshark-bugs] [Bug 8279] Add support for Android Logcat logs, text files and
Comment # 27
on bug 8279
from Guy Harris
(In reply to comment #25)
> Opening Text/Binary file is not "must be" feature for me, but this is very
> comfortable. Also binary file can be used as first step to create/modify
> packet by Packet Editor.
No, because
1) there already *is* a first step - Jakub's packet editor code;
2) a packet editor isn't an arbitrary binary file editor, it's a *packet*
editor, so it only edits files containing packets, and we *already* support
reading those.
> You may not use that functionality, but apply them
> you do not break anything,
You add more code that has to be maintained, and that gets people to ask for
more features, unless we can ignore any and all bugs and feature requests
concerning that functionality.
> With Wireshark you can filtering text
> file, for example searching with line contain Windows newline in Linux
> format os text file.
With microEmacs I can search for lines containing CR-LF. There's probably a
way to do it in GNU EMACS as well.
> I treat text file as PNG file.
I tried to do that - treat file.c as a PNG file, by copying it to
/tmp/yeahright.png - and Preview said, not surprisingly:
The file “yeahright.png” could not be opened.
It may be damaged or use a file format that Preview doesn’t recognize.
when I tried to open it.
Or did you mean something else by "I treat text file as PNG file."?
> Or maybe ask to change Wireshark from "protocols analyser" to
> "protocols/formats analyser"? As I know Wireshark is more than network (Is
> USB a network?).
Is there a USB protocol? Yes. If you search for
"bus protocol"
in Google, there are "About 325,000 results", so buses, like networks, use
protocols.
> I wonder why cosmetic feature is very popular to debate while normal feature
> is not :)
This isn't a "cosmetic feature". It's a significant change to what Wireshark
*is*. It's even more significant than just adding support for reading
*specific types* of files, containing data that have medium types assigned to
them and dissectors for those medium types - it's turning it into a hex editor
(or, at least viewer) and a text editor (or, at least, viewer).
> > Why on earth should I try opening an arbitrary text file or binary file with a
> > protocol analyser?
>
> To see it content, use packet editor to change it to something else (fix).
How is that better than using a text editor or a hex editor to change something
in the a text or binary file?
> Also put your comment in interesting place (example: "John, this field
> should be 65").
As Wireshark is a packet viewer/editor, and as the packet capture files it
reads don't support attaching comments to arbitrary places in files, comments
can only be attached to "records"; they can't be put in arbitrary places.
> Hmm... Emacs, right? I do not use it... but please tell me... why you can
> play Tetris via Emacs? :)
Because a number of early versions of Emacs and Emacs-like editors were written
in LISP, and a lot of LISP programmers like LISP-based environments such as
LISP machines; GNU Emacs is best thought of as a LISP environment that happens
to contain some primitives to support writing editors rather than as a text
editor that happens to be extensible in LISP.
You are receiving this mail because:
- You are watching all bug changes.
