From: Raymond Scholz <ray-2002@zonix.de>
Subject: Re: funny problems with nnmail-cache and split-fancy-with-parent
Date: Sun, 12 May 2002 22:33:48 +0200 [thread overview]
Message-ID: <gd.878z6pkswj.fsf@mde1.zonix.de> (raw)
In-Reply-To: <87r8ko822k.fsf@alum.wpi.edu>
Josh Huber <huber@alum.wpi.edu> writes:
> diff -u -r6.39 nnmail.el
> --- lisp/nnmail.el 2002/04/29 20:08:18 6.39
> +++ lisp/nnmail.el 2002/05/07 14:29:55
> @@ -1469,13 +1469,13 @@
> (let ((g nil))
> (cond (grp
> (setq g grp))
> + ((and (boundp 'group-art) group-art (listp group-art))
> + (setq g (caar group-art)))
> ((and (boundp 'group) group)
> (setq g group))
> ((and (boundp 'group-art-list) group-art-list
> (listp group-art-list))
> (setq g (caar group-art-list)))
> - ((and (boundp 'group-art) group-art (listp group-art))
> - (setq g (caar group-art)))
> (t (setq g "")))
> (unless (gnus-buffer-live-p nnmail-cache-buffer)
> (nnmail-cache-open))
>
> Works for me, but after looking at this -- shouldn't there be a better
> interface into nnmail-cache-insert? We should go through and find all
> the places which call it, which is only 10 places, and use the
> optional argument for group name if possible. checking for bound
> symbols and using heuristics to get the group name seems a little
> hackish to me ;) (no offense to Kai!)
Hi Josh!
As you may have read on gnus-bug <gg.87offmz7ul.fsf@mde1.zonix.de>,
your patch is causing problems with my setup (two Gcc headers with
different backends (nnfolder and nnml).
Kai asked me to bring up this issue on *ding* again. I'm afraid I
cannot contribute a lot (apart from bug reports) because of my limited
knowlegde of what is going on in nnmail.el.
Here's the backtrace again:
,----
| Debugger entered--Lisp error: (wrong-type-argument listp "sent.mail.home.2002")
| nnmail-cache-insert("<.87lmarby9j.fsf@mde1.zonix.de>")
| nnml-request-accept-article("mail.other" "" t)
| gnus-request-accept-article("nnml:mail.other" "nnml:" t t)
| gnus-inews-do-gcc()
| run-hooks(message-sent-hook)
| message-send(nil)
| message-send-and-exit(nil)
| call-interactively(message-send-and-exit)
`----
Cheers, Ray
--
It's clear that whoever set up the font colorings for most programming
modes has seen too many Peter Max posters, or did more acid than I did
in the 60's. (Charles R. Martin in gnu.emacs.help)
next prev parent reply other threads:[~2002-05-12 20:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 19:58 Josh Huber
2002-05-03 11:17 ` Kai Großjohann
2002-05-03 15:26 ` Josh Huber
2002-05-03 17:47 ` Kai Großjohann
2002-05-03 18:39 ` Josh Huber
2002-05-05 11:56 ` Kai Großjohann
2002-05-07 14:28 ` Josh Huber
2002-05-07 14:34 ` Josh Huber
2002-05-07 15:22 ` Kai Großjohann
2002-05-07 16:31 ` Josh Huber
2002-05-07 15:24 ` Kai Großjohann
2002-05-07 16:29 ` Josh Huber
2002-05-12 20:33 ` Raymond Scholz [this message]
2002-05-13 14:11 ` Josh Huber
2002-05-14 21:12 ` Raymond Scholz
2002-05-15 14:36 ` Josh Huber
2002-05-15 16:01 ` Raymond Scholz
2002-05-15 17:21 ` Josh Huber
2002-05-18 19:03 ` Kai Großjohann
2002-05-20 14:08 ` Josh Huber
2002-05-20 14:35 ` Kai Großjohann
2002-05-20 18:34 ` Josh Huber
2002-05-20 19:01 ` Kai Großjohann
2002-05-20 19:16 ` Paul Jarc
2002-05-20 20:08 ` Kai Großjohann
2002-05-20 21:32 ` Josh Huber
2002-05-21 10:44 ` Kai Großjohann
2002-05-21 12:48 ` Raymond Scholz
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=gd.878z6pkswj.fsf@mde1.zonix.de \
--to=ray-2002@zonix.de \
--cc=rscholz@zonix.de \
/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).