Wireshark-bugs: [Wireshark-bugs] [Bug 3296] Export to File Omits File Type Extension
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 18 May 2015 19:46:34 +0000

changed bug 3296


What Removed Added
CC   raysatiro@yahoo.com

Comment # 3 on bug 3296 from 
Version 1.12.5 (v1.12.5-0-g5819e5b from master-1.12)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built May 12 2015),
with
AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.

------------------------------------

I'm having this problem in Windows. When I'm exporting as a plain text file and
I type foo, I'd expect it saved as foo.txt but instead it's saved as just foo.
Wireshark's way is different from a lot of other programs.

If the concern is that the user may provide some other extension is it possible
to add a heuristic for Windows similar to the way Notepad works, where Notepad
will only append the default extension to the filename if the user didn't
supply an extension.

You are receiving this mail because:
  • You are the assignee for the bug.
  • You are watching all bug changes.