From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Wrong number of articles from completely read group
Date: Sun, 02 Jan 2011 08:10:36 +0100 [thread overview]
Message-ID: <m34o9rdbmb.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <874oa8xoky.fsf@member.fsf.org>
Tassilo Horn <tassilo@member.fsf.org> writes:
> I think that applies to any backend that allows for modifications,
> right?
Yes.
> In org-gnus.el, I have this really beatiful snippet to reliably
> open a summary buffer at least showing ARTICLE (article number or
> message id).
[...]
> It works, but is there something better that doesn't rely on some
> optional feature (like the registry) and works independently from the
> used backend?
Not at the moment, but there should be.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-02 7:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 16:56 Tommy Kelly
2010-12-20 17:05 ` Lars Magne Ingebrigtsen
2010-12-20 18:45 ` Tommy Kelly
2010-12-20 22:21 ` Steinar Bang
2010-12-20 22:43 ` Tommy Kelly
2010-12-20 23:19 ` Steinar Bang
2010-12-21 0:00 ` Tommy Kelly
2010-12-21 0:38 ` Tibor Simko
2010-12-21 1:22 ` Tommy Kelly
2010-12-21 16:04 ` Tommy Kelly
2010-12-20 18:54 ` Tassilo Horn
2011-01-02 7:10 ` Lars Magne Ingebrigtsen [this message]
2010-12-20 17:05 ` Tommy Kelly
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=m34o9rdbmb.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).