From: Andreas Seltenreich <andreas+ding@gate450.dyndns.org>
To: ding@gnus.org
Subject: Re: Broken IMAP search with nnir.el
Date: Sun, 25 Mar 2007 07:54:21 +0200 [thread overview]
Message-ID: <87odmhzx4i.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <87odmkxba6.fsf@mocca.josefsson.org> (Simon Josefsson's message of "Fri\, 23 Mar 2007 15\:52\:17 +0100")
Simon Josefsson writes:
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> Yes, the displayed message was part of a former search result. Is it
>> possible to disable this caching?
gnus-backlog-shutdown tends to clean up this kind of caching mess for
me.
> I think it might be easier to have nnir never re-use article numbers.
> But I'm not familiar enough with nnir to fix this.
I'm afraid this would break solid groups, which work ok for engines
that support ordering of returned articles by delivery-date or
something comparable instead of "Score".
>> And another thing: Is it possible to jump from a search result message
>> to the original message, so that the correct Posting Styles and Group
>> Parameters are used when I want to reply/forward/whatsoever?
,----[ C-h f gnus-summary-nnir-goto-thread RET ]
| gnus-summary-nnir-goto-thread is an interactive Lisp function in `nnir.el'.
| (gnus-summary-nnir-goto-thread)
|
| Only applies to nnir groups. Go to group this article came from
| and show thread that contains this article.
`----
regards,
andreas
next prev parent reply other threads:[~2007-03-25 5:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 14:19 Tassilo Horn
2007-03-22 14:26 ` Simon Josefsson
2007-03-22 15:18 ` Tassilo Horn
2007-03-23 14:52 ` Simon Josefsson
2007-03-25 5:54 ` Andreas Seltenreich [this message]
2007-03-25 20:42 ` Andreas Seltenreich
2007-03-26 8:28 ` Tassilo Horn
2007-03-26 17:39 ` Andreas Seltenreich
2007-03-26 17:53 ` Tassilo Horn
2007-03-26 8:30 ` Tassilo Horn
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=87odmhzx4i.fsf@gate450.dyndns.org \
--to=andreas+ding@gate450.dyndns.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).