Your message dated Fri, 25 Mar 2005 16:01:32 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300123: xterm: alt-. gives wrong signal to zsh
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Mar 2005 19:45:25 +0000
>From [EMAIL PROTECTED] Thu Mar 17 11:45:23 2005
Return-path: <[EMAIL PROTECTED]>
Received: from 220-244-116-62-nsw.tpgi.com.au (localhost) [220.244.116.62]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DC0vq-0008EH-00; Thu, 17 Mar 2005 11:45:22 -0800
Received: from nicko by localhost with local (Exim 3.36 #1 (Debian))
id 1DC0vn-0001ge-00
for <[EMAIL PROTECTED]>; Fri, 18 Mar 2005 06:45:19 +1100
Resent-From: [EMAIL PROTECTED]
Resent-Date: Fri, 18 Mar 2005 06:45:19 +1100
Resent-Message-ID: <[EMAIL PROTECTED]>
Resent-To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Received: from localhost ([127.0.0.1] ident=root)
by localhost with esmtp (Exim 3.36 #1 (Debian))
id 1CQle9-0001zj-00
for <[EMAIL PROTECTED]>; Sun, 07 Nov 2004 22:55:49 +1100
Received: from mail.acay.com.au [203.88.251.3]
by localhost with IMAP (fetchmail-5.9.11)
for [EMAIL PROTECTED] (single-drop); Sun, 07 Nov 2004 22:55:49 +1100
(EST)
Received: from amailsyd.tel-pacific.com ([203.88.255.61])
by aspoolsyd.tel-pacific.com with esmtp (Exim 4.30)
id 1CQlbZ-0005rf-MB
for [EMAIL PROTECTED]; Sun, 07 Nov 2004 22:53:09 +1100
Received: from [203.88.255.24] (helo=mailgate2.mci.tel-pacific.com)
by amailsyd.tel-pacific.com with esmtp (Exim 4.30)
id 1CQlcd-0007me-6t
for [EMAIL PROTECTED]; Sun, 07 Nov 2004 22:54:15 +1100
Received: from localhost (220-244-116-62-nsw.tpgi.com.au [220.244.116.62])
by mailgate2.mci.tel-pacific.com (8.11.6/8.11.6) with ESMTP id
iA7BjDK02374
for <[EMAIL PROTECTED]>; Sun, 7 Nov 2004 22:45:13 +1100
Received: from nicko by localhost with local (Exim 3.36 #1 (Debian))
id 1CQlTm-0001yY-00; Sun, 07 Nov 2004 22:45:06 +1100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Nick Croft <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xterm: alt-. gives wrong signal to zsh
X-Mailer: reportbug 3.1
Date: Sun, 07 Nov 2004 22:45:06 +1100
Message-Id: <[EMAIL PROTECTED]>
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
X-Bogosity: Ham, tests=bogofilter, spamicity=0.00e+00, version=0.92.8
Resent-Sender: Nick Croft <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: xterm
Version: 4.3.0.dfsg.1-8
Severity: important
Upgrading to xterm 4.3.0 caused the (often used) alt-. to send the wrong signal
to zsh (4.0.4 and later) in viins mode. Alt-. is used in zsh to insert the
last argument of the previous cmd line.
The behaviour is as expected in emacs-mode. More importantly it is as expected
in viins mode in any other shell or the console. Downgrading to 4.0.4 `fixed'
the problem.
Also the colors reverted from 16 to 8 with this upgrade. I have since
downgraded.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.21-xfs
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Versions of packages xterm depends on:
ii debconf 1.4.39 Debian configuration management sy
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libfreetype6 2.1.7-2.2 FreeType 2 font engine, shared lib
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii libxaw7 4.3.0.dfsg.1-8 X Athena widget set library
ii xlibs 4.3.0.dfsg.1-8 X Window System client libraries m
-- no debconf information
---------------------------------------
Received: (at 300123-done) by bugs.debian.org; 25 Mar 2005 21:01:33 +0000
>From [EMAIL PROTECTED] Fri Mar 25 13:01:33 2005
Return-path: <[EMAIL PROTECTED]>
Received: from cpe-65-26-182-85.indy.res.rr.com (sisyphus.deadbeast.net)
[65.26.182.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DEvvx-00066J-00; Fri, 25 Mar 2005 13:01:33 -0800
Received: by sisyphus.deadbeast.net (Postfix, from userid 1000)
id 5AF3C68C019; Fri, 25 Mar 2005 16:01:32 -0500 (EST)
Date: Fri, 25 Mar 2005 16:01:32 -0500
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#300123: xterm: alt-. gives wrong signal to zsh
Message-ID: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="6cMF9JLEeZkfJjkP"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--6cMF9JLEeZkfJjkP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Nov 07, 2004 at 10:45:06PM +1100, Nick Croft wrote:
> Package: xterm
> Version: 4.3.0.dfsg.1-8
> Severity: important
>=20
> Upgrading to xterm 4.3.0 caused the (often used) alt-. to send the wrong =
signal
> to zsh (4.0.4 and later) in viins mode. Alt-. is used in zsh to insert t=
he
> last argument of the previous cmd line.=20
>=20
> The behaviour is as expected in emacs-mode. More importantly it is as exp=
ected
> in viins mode in any other shell or the console. Downgrading to 4.0.4 `fi=
xed'
> the problem.
>=20
> Also the colors reverted from 16 to 8 with this upgrade. I have since
> downgraded.
You already filed this as #280118.
[The following is a form letter.]
Hello,
You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.
While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.
One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name. A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports. This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report. This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers. The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports. (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)
Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System. (If you already do use
"reportbug", please see below.)
One way to install reportbug is with "apt-get"; for
example:
# apt-get install reportbug
The "reportbug" command has a few different modes that cater to different
levels of user expertise. If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.
$ reportbug --mode=3Dnovice
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.
$ reportbug
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
The reportbug command is extensively documented in its usage message and
manual page. Commands to view these pieces of documentation are:
$ reportbug --help | more
$ man reportbug
(The output of the above commands has been omitted from this message.)
If you do use reportbug, but are so daunted by the large number of bugs
already filed against a package that you feel you cannot search for a
duplicate, please note that reportbug has a (f)ilter feature that enables
you to use a keyword search to limit the number of bugs reported. (If
you're feeling ambitious, the filter feature also accepts a regular
expression.) For example, if you'd like to report a SEGV (segfault), you
might filter based on the term "SEGV". If you're having trouble upgrading
a package, you might filter based on "upgrad" (to catch both "upgrade" and
"upgrading"). Some package maintainers retitle bugs to contain keywords so
as to facilitate better filtering and convey more useful information, since
a bug report with a title of "broken" or the like is not very useful to
anyone.
We appreciate you taking the time to help package maintainers serve you
better by reducing the amount of time they need to spend coping with
duplicate bug reports.
Thanks for using the Debian system!
--=20
G. Branden Robinson |
Debian GNU/Linux | If ignorance is bliss,
[EMAIL PROTECTED] | is omniscience hell?
http://people.debian.org/~branden/ |
--6cMF9JLEeZkfJjkP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iEYEARECAAYFAkJEfCwACgkQ6kxmHytGonwcQQCePtr3emOgoPgKb3H2papCzWhd
jA4An3AtvuoAYl2mCEd07o1QXDekuZje
=et/L
-----END PGP SIGNATURE-----
--6cMF9JLEeZkfJjkP--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
