Your message dated Fri, 29 Jul 2005 15:49:45 +0900 (JST)
with message-id <[EMAIL PROTECTED]>
and subject line Bug#58992: viper-mode and gnus cause frequent error messages
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; 25 Feb 2000 15:21:53 +0000
Received: (qmail 4591 invoked from network); 25 Feb 2000 15:21:52 -0000
Received: from ha1.rdc2.occa.home.com (HELO mail.rdc2.occa.home.com) ([EMAIL 
PROTECTED])
  by master.debian.org with SMTP; 25 Feb 2000 15:21:52 -0000
Received: from cc74074-a.flrtn1.occa.home.com ([24.0.205.112])
          by mail.rdc2.occa.home.com (InterMail v4.01.01.00 201-229-111)
          with ESMTP
          id <[EMAIL PROTECTED]>
          for <[EMAIL PROTECTED]>; Fri, 25 Feb 2000 07:21:51 -0800
Received: (from [EMAIL PROTECTED])
        by cc74074-a.flrtn1.occa.home.com (8.9.3/8.9.3/Debian 8.9.3-6) id 
HAA18065
        for [EMAIL PROTECTED]; Fri, 25 Feb 2000 07:21:51 -0800
Date: Fri, 25 Feb 2000 07:21:51 -0800
From: J Robert Ray <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: viper-mode and gnus cause frequent error messages
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i

Package: xemacs21
Version: 21.1.8-2

When running xemacs with viper-mode enabled, I frequently get the
following error message while using gnus:

(1) (error/warning) Error in `post-command-hook' (setting hook to nil): 
(wrong-type-argument extent-live-p #<exten\t>)

The number (1) increases each time the error message is emitted.

If I remove the following lines from my .emacs (as shown), the error
messages do not appear:

;; (setq viper-mode t)
;; (require 'viper)

The error messages occur while doing many tasks, including reading
mail or news messages (selecting a new article to read), or while
composing mail.  If it occurs when I am selecting a mail message to
read, the body of the mail will appear after I select the article a
second time.

I'm running gnus 5.8.3-6, on potato.
Linux cc74074-a 2.2.14 #1 SMP Sat Feb 5 17:51:03 PST 2000 i686 unknown
---------------------------------------
Received: (at 58992-done) by bugs.debian.org; 29 Jul 2005 06:51:29 +0000
>From [EMAIL PROTECTED] Thu Jul 28 23:51:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from omls-1a.kuins.net [130.54.130.66] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1DyOiO-0002BY-00; Thu, 28 Jul 2005 23:51:28 -0700
Received: from imls-1a.kuins.net (imls-1a.imail.kuins.net [10.224.253.3] (may 
be forged))
        by omls-1a.kuins.net (8.12.10/8.12.7) with ESMTP id j6T6pRLc001088
        for <[EMAIL PROTECTED]>; Fri, 29 Jul 2005 15:51:27 +0900
Received: from imls-1a.kuins.net (localhost.localdomain [127.0.0.1])
        by imls-1a.kuins.net (8.12.11/8.12.10) with ESMTP id j6T6pQAf005777
        for <[EMAIL PROTECTED]>; Fri, 29 Jul 2005 15:51:26 +0900
Received: from penold (h147.88.228.10.30038.vlan.kuins.net [10.228.88.147])
        by imls-1a.kuins.net (8.12.11/8.12.10) with ESMTP id j6T6pQwU005774;
        Fri, 29 Jul 2005 15:51:26 +0900
Received: from localhost (penold [127.0.0.1])
        by penold (Postfix) with ESMTP id 7CAF07670;
        Fri, 29 Jul 2005 15:51:53 +0900 (JST)
Date: Fri, 29 Jul 2005 15:49:45 +0900 (JST)
Message-Id: <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#58992: viper-mode and gnus cause frequent error messages
From: OHURA Makoto <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
X-Mailer: Mew version 4.2.52 on XEmacs 21.4.17 (Jumbo Shrimp)
Mime-Version: 1.0
Content-Type: Multipart/Signed; protocol="application/pgp-signature";
 micalg=pgp-sha1;
 boundary="--Security_Multipart(Fri_Jul_29_15_49_45_2005_356)--"
Content-Transfer-Encoding: 7bit
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-Level: 
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

----Security_Multipart(Fri_Jul_29_15_49_45_2005_356)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

  Hi.

From: Shyamal Prasad <[EMAIL PROTECTED]>
Subject: Bug#58992: viper-mode and gnus cause frequent error messages
Date: Sat, 23 Jul 2005 12:03:57 -0700
> I am not a regular user of viper mode (but actually an avid vi fan
> even though I use emacs, so I just use vi when I want those key
> bindings ;-).
>
> I have tried using viper mode and gnus together (and I am writing this
> email in such a mode) and do not see any problems in sarge.
>
> This bug is over 5 years old, I would strongly suggesting closing it
> since the original fault (in post-command-hook) clearly does not exist
> anymore.

  O.K. I close this bug.

  Thanks.

----
  OHURA Makoto: [EMAIL PROTECTED](Debian Project)
                [EMAIL PROTECTED](LILO/Netfort)
  GnuPG public key: http://www.netfort.gr.jp/~ohura/gpg.asc.txt
                    1024D/77DCE083
        fingerprint: 54F6 D1B1 2EE1 81CD 65E3  A1D3 EEA2 EFA2 77DC E083
  http://www.netfort.gr.jp/~ohura/

----Security_Multipart(Fri_Jul_29_15_49_45_2005_356)--
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBC6dGQ7qLvonfc4IMRAr6JAKDKd6Zun/Cc74duZhlgj5AlnMkycACfZERY
4isWn4xzkwUUGY3BSHsZ+oc=
=ZMgf
-----END PGP SIGNATURE-----

----Security_Multipart(Fri_Jul_29_15_49_45_2005_356)----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to