Wireshark-bugs: [Wireshark-bugs] [Bug 8176] New: Restore the <Ctrl>X shortcut to Cut in the filt
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 08 Jan 2013 20:51:12 +0000
Bug ID 8176
Summary Restore the <Ctrl>X shortcut to Cut in the filter textbox per bugs 5115 and 5231
Classification Unclassified
Product Wireshark
Version 1.9.x (Experimental)
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Wireshark
Assignee bugzilla-admin@wireshark.org
Reporter turney_cal@emc.com
Attachment #9783 Flags review_for_checkin? 

Created attachment 9783 [details]
This patch restores <Ctrl>x to Cut and <Ctrl>d to 'Ignore packet'.

Build Information:
Version 1.9.0 (SVN Rev Unknown from unknown)

Copyright 1998-2013 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 (32-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_2), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Jan  7 2013), with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.

Built using Microsoft Visual C++ 10.0 build 40219
==============================================================================


--
Once again someone has changed the <Ctrl>x shortcut from its commonly accepted
function of Cut to Ignore.  As Guy Harris stated in Bug #5115 "we shouldn't be
stealing common command shortcuts for our own purposes." This same issue was
also reported in #5231 and was marked as Resolved but here we go again.

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