From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: GNUS Mailing List <ding@gnus.org>
Subject: Re: Bug sending messages unplugged
Date: 23 Nov 1998 13:53:09 -0800 [thread overview]
Message-ID: <x7g1bakrei.fsf@des.castles.com> (raw)
In-Reply-To: Colin Rafferty's message of "23 Nov 1998 14:58:32 -0500"
>>>>> On 23 Nov 1998 14:58:32 -0500, Colin Rafferty <craffert@ms.com> said:
>> Signaling: (wrong-type-argument integer-or-marker-p nil)
>> lazy-shot-fontify-internal(#<buffer "*sent mail*<2>"> nil nil nil "")
>> lazy-shot-lock-extent(#<destroyed extent> nil)
>> lazy-shot-redisplay-function(#<destroyed 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).
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.
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-11-23 21:53 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 [this message]
1998-11-24 10:03 ` Jan Vroonhof
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=x7g1bakrei.fsf@des.castles.com \
--to=wjhardaker@ucdavis.edu \
--cc=ding@gnus.org \
/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).