Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Getting rid of the zombies in dynamically created groups
Date: Wed, 26 Sep 2007 20:38:20 +0200	[thread overview]
Message-ID: <v94phhqnkz.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3wsudy1ni.fsf@cerebro.fsfeurope.org>

On Wed, Sep 26 2007, Georg C. F. Greve wrote:

> in the course of integration of org mode with mairix and gnus, I came
> across the need for Gnus to enter a group that is recreated dynamically
> by mairix -- so Gnus will need to forget everything about the group when
> entering it, and read it afresh.

How about using ephemeral groups?  Here's an example for mbox, I don't
know if something similar can be done with maildir.

--8<---------------cut here---------------start------------->8---
(defvar rs-gnus-debian-bug-mbox-string
  "http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%s&mbox=yes")

(defun rs-gnus-read-bug-group (number &optional mbox-url)
  "Browse Debian Bug with NUMBER as ephemeral group."
  (interactive (list
		(read-string "Enter Bug number: "
			     (thing-at-point 'word)
			     nil)))
  (when (stringp number)
    (setq number (string-to-number number)))
  (let ((tmpfile (make-temp-file "rs-gnus-temp-group-")))
    (with-temp-file tmpfile
      (url-insert-file-contents
       (format (or mbox-url rs-gnus-debian-bug-mbox-string) number))
      (write-region (point-min) (point-max) tmpfile)
      (gnus-group-read-ephemeral-group
       "rs-gnus-read-bug"
       `(nndoc ,tmpfile
	       (nndoc-article-type mbox))))
    (delete-file tmpfile)))
--8<---------------cut here---------------end--------------->8---

>    Gnus developers couldn't really help, see:
>     http://article.gmane.org/gmane.emacs.gnus.general/65248

Well, you could give them more than one day before stating the
couldn't help.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2007-09-26 18:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 13:52 Georg C. F. Greve
2007-09-26 18:38 ` Reiner Steib [this message]
2007-09-26 22:38   ` Georg C. F. Greve
2007-09-27  6:12     ` Reiner Steib
2007-09-27 21:35       ` Georg C. F. Greve
2007-10-04  8:04 ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) David
2007-10-04 16:29   ` released mairix backend nnmairix.el Reiner Steib
2007-10-05  9:15     ` David
2007-10-05 16:41       ` Reiner Steib
2007-10-06 14:24       ` Georg C. F. Greve
2007-10-06 18:59         ` Bastien
2007-10-06 21:20           ` David
2007-10-06 23:19             ` Bastien
2007-10-07 16:09               ` David
2007-10-08  9:33                 ` Bastien
2007-10-06 21:17         ` David
2007-10-06 23:17           ` Bastien
2007-10-07 11:12           ` Georg C. F. Greve
2007-10-07 15:53             ` David
2007-10-08  9:33               ` Bastien
2007-10-04 16:48   ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) Bastien
2007-10-04 17:18     ` released mairix backend nnmairix.el Bastien
2007-10-05  9:46       ` David
2007-10-05 12:00         ` Bastien
2007-10-04 23:54   ` Bastien

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=v94phhqnkz.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).