Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: Bug sending messages unplugged
Date: 24 Nov 1998 11:03:56 +0100	[thread overview]
Message-ID: <by67c52yr7.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Wes Hardaker's message of "Mon, 23 Nov 1998 21:54:16 GMT"

Wes Hardaker <wjhardaker@ucdavis.edu> writes:

> I submitted a bug report to Lars, and he said its lazy-shot's fault
> and I should submit the bug to that author instead.  I didn't want to
> do that until determining the exact "fault" first, since I suspect
> they'd say its was Gnus' fault.

It is too late now. I have seen it :-)

> >> lazy-shot-fontify-internal(#<buffer "*sent mail*<2>"> nil nil nil "")
> >> lazy-shot-lock-extent(#<destroyed extent> nil)
> >> lazy-shot-redisplay-function(#<destroyed extent>)

It is indeed a Lazy-shot bug. It is fixed in 21.0. Gnus is probably
copying parts of the buffer around into strings and lazy-shot does not
like that very much. However this is also a good indication Gnus is
using buffer-substring somewhere where it probably needs
buffer-substring-noproperties. 

===================================================================
RCS file: /usr/CVSroot/XEmacs/xemacs-packages/oa/edit-utils/lazy-shot.el,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- oa/edit-utils/lazy-shot.el  1998/01/14 06:36:17     1.1
+++ oa/edit-utils/lazy-shot.el  1998/04/18 14:31:24     1.2
@@ -157,7 +157,7 @@
 (defun lazy-shot-lock-extent (extent stealth)
   "Font-lock the EXTENT. Called from redisplay-trigger functions and
 stealth locking functions"
-   (when (extent-live-p extent)
+  (when (and (extent-live-p extent) (null (extent-detached-p extent)))
      (let ((start (extent-start-position extent))
           (end   (extent-end-position extent))
           (buffer (extent-object extent)))


> 
> Colin> This is very weird.  Is this the entire stack trace?  It seems a
> Colin> little truncated.
> 
> Yes it is, actually.  I get them too.  The odd thing is that I only
> get them when sending news, not mail.
> 
> Anyway, I think what is happening is that gnus places the articles in
> a new buffer (*mail* oddly enough, since its news) and then font lock
> is swinging on them after that.  What I'm not sure of is if its
> happening before or after the article gets sent.  I think its before
> (which is bad) not after (which would be bad for me, because it means
> I've sent multiple copies of messages to my newserver because of the
> above bug).
> 
> -- 
> "Ninjas aren't dangerous.  They're more afraid of you than you are of them."
> 

-- 
Jan Vroonhof                    http://www.math.ethz.ch/~vroonhof/
Mathematik,                               vroonhof @  math.ethz.ch
HG E16, ETH-Zentrum,                      Tel: +41-1-6325456/25154
Raemistrasse 101, CH-8092 Zuerich.              Fax: +41-1-6321085


  reply	other threads:[~1998-11-24 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-23 19:44 Markus Dickebohm
1998-11-23 19:58 ` Colin Rafferty
1998-11-23 21:53   ` Wes Hardaker
1998-11-24 10:03     ` Jan Vroonhof [this message]
1998-11-25 22:12       ` Wes Hardaker
1998-11-23 23:08   ` Markus Dickebohm
1998-11-24  0:05     ` Wes Hardaker
1998-11-24 10:11   ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=by67c52yr7.fsf@bolzano.math.ethz.ch \
    --to=vroonhof@math.ethz.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).