Your message dated Sat, 30 Jan 2016 18:16:42 +0000
with message-id <[email protected]>
and subject line Bug#811007: Removed package(s) from unstable
has caused the Debian Bug report #288511,
regarding xchat: please make completion_amount editable in the gui
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
288511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=288511
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xchat
Version: 2.4.1-0.1
Severity: normal
xchat's "new" nick-completion behaviour is extremely annoying. It
does not behave in the same way as one expects tab completion to
work (like, from bash or any other sane piece of software) -- when
there are multiple possible completions.
When there are multiple possible completions, it should *NOT* complete
with the first one that pops into its stupid head, it should refuse to
complete at all, or beep, or pop up a list, or do *SOMETHING* to indicate
that you have a problem and need to type further before you can complete
successfully.
It should also leave the ****ing cursor where it was, so I at least get
the option of continuing to type the nick without having to backspace over
the ridiculously long nick that it has decided I wanted, and without having
to tab through the ridiculously long list of similar nicks that may just
happen to exist.
I've noticed lots of people mistyping nicks since this was introduced.
Almost all of them are using xchat. Coincidence? I think not.
The current behaviour is deeply, painfully and obviously wrong. And I
don't mean "wrong" in the way that saying 2+2=5 is wrong. I mean wrong
in the way that pulling spiders legs off to see whether they can still
walk, sneaking into the office at night and replacing all the workstations
with Windows Me boxes, or installing BSOD screensavers onto clueless
newbies' windows machines is wrong.
Unnecessary pain. Please make it go away :-)
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8nwp2
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages xchat depends on:
ii libatk1.0-0 1.8.0-4 The ATK accessibility toolkit
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libglib2.0-0 2.4.8-1 The GLib library of C routines
ii libgtk2.0-0 2.4.13-1 The GTK+ graphical user interface
ii libpango1.0-0 1.6.0-3 Layout and rendering of internatio
ii libperl5.8 5.8.4-3 Shared Perl library
ii libssl0.9.7 0.9.7e-2 SSL shared libraries
ii libx11-6 4.3.0.dfsg.1-8 X Window System protocol client li
ii python2.3 2.3.4-18 An interactive high-level object-o
ii tcl8.4 8.4.9-1 Tcl (the Tool Command Language) v8
ii xchat-common 2.4.1-0.1 Common files for X-Chat
ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.8.8-7.3+rm
Dear submitter,
as the package xchat has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/811007
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
