From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/4755 Path: main.gmane.org!not-for-mail From: Kai Grossjohann Newsgroups: gmane.emacs.gnus.general Subject: Re: sgnus-0.26 + font-lock + lazy-lock == problem? Date: 17 Jan 1996 09:29:39 +0100 Organization: Universitaet Dortmund, CS Dept, Chair 6 Sender: grossjoh@dusty.informatik.uni-dortmund.de Message-ID: References: Reply-To: Kai Grossjohann NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1035145458 30694 80.91.224.250 (20 Oct 2002 20:24:18 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:24:18 +0000 (UTC) Cc: ding@ifi.uio.no Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miranova.com (8.7.3/8.6.9) with SMTP id CAA02416 for ; Wed, 17 Jan 1996 02:06:20 -0800 Original-Received: from waldorf.informatik.uni-dortmund.de (waldorf.informatik.uni-dortmund.de [129.217.4.42]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Wed, 17 Jan 1996 09:29:48 +0100 Original-Received: from dusty.informatik.uni-dortmund.de by waldorf.informatik.uni-dortmund.de with SMTP (Sendmail 8.6.11/UniDo 2.0.43) id JAA24019; Wed, 17 Jan 1996 09:29:42 +0100 Original-Received: by dusty.informatik.uni-dortmund.de id AA23808; Wed, 17 Jan 96 09:29:41 +0100 Original-To: Steven L Baur In-Reply-To: Steven L Baur's message of 16 Jan 1996 09:08:54 -0800 Original-Lines: 23 Xref: main.gmane.org gmane.emacs.gnus.general:4755 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:4755 >>>>> "Kai" =3D=3D Kai Grossjohann >>>>> writes: Kai> using the above combination (font-lock as of Emacs 19.30, Kai> lazy-lock 2.02), I see an interaction between sgnus and Kai> font-locking. >>>>> On 16 Jan 1996 09:08:54 -0800, Steven L Baur >>>>> said: Steven> I'm using lazy-lock 2.00, and I've noticed a problem only Steven> with Emacs 19.30 (it does not occur with XEmacs). After Steven> sending a message, the buffer returned to has its colors Steven> wiped out. I'm now suspecting a lazy lock interaction Steven> because undisplayed portions of the buffer aren't changed. Exactly this is what I'm suspecting, too! Only that it seems to occur at different times for me than it does for you. I don't use XEmacs so can't check what happens there. kai -- I like both kinds of music.