Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Indexing Gnus (and other...) mails
Date: Thu, 09 Apr 2009 20:34:43 +0200	[thread overview]
Message-ID: <87y6u9y8u4.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87ocv6uwko.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Thu, 09 Apr 2009 09:15:35 +0200")

Tassilo Horn <tassilo@member.fsf.org> writes:

> And for speading up searches in the whole message including BODY,
> dovecot offers plugins:
>
>   http://wiki.dovecot.org/Plugins/FTS
>
> So I'd love to see a better support for IMAP SEARCH in Gnus.  nnir
> works, but sometimes it's a bit humpy.  For example if I search for a
> string the second time each result message appears two times in the
> search result group.
>
> And what bothers me most: When I want to see a result message in the
> original group (I want to reply using the groups posting styles and
> parameters) I hit G T on the message (gnus-summary-nnir-goto-thread)
> but then I'm queried for my username / password for the local imap
> server.  Those informations are already in my .authinfo...

Ok, I have fixed that for me like by redefining g-s-n-g-t like that:

--8<---------------cut here---------------start------------->8---
(defun gnus-summary-nnir-goto-thread ()
  "Redefines the function from nnir.el."
  (interactive)
  (unless (eq 'nnir (car (gnus-find-method-for-group gnus-newsgroup-name)))
    (error "Can't execute this command unless in nnir group."))
  (let* ((cur (gnus-summary-article-number))
         (group (nnir-artlist-artitem-group nnir-artlist cur))
         (mid (mail-header 'message-id
                           (progn
                             (gnus-summary-select-article t)
                             (with-current-buffer gnus-article-buffer
                               (goto-char (point-min))
                               (mail-header-extract-no-properties))))))
    (gnus-group-read-group 1 t group nil)
    (gnus-summary-refer-article mid)
    (gnus-summary-refer-thread)
    ;; TODO: Is there nothing like limiting to the current thread?
    ))
--8<---------------cut here---------------end--------------->8---

This works good for me and maybe it's the right approach, too.  I don't
quite understand why nnir uses an epheneral group and black article
number magic while Gnus will do the right thing given a message-id
anyway.

Comments?

Bye,
Tassilo



  parent reply	other threads:[~2009-04-09 18:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87y6ubo5th.fsf@an-dro.enstb.org>
     [not found] ` <87ab6rbi5p.fsf@thinkpad.tsdh.de>
     [not found]   ` <mailman.4911.1239209214.31690.info-gnus-english@gnu.org>
2009-04-08 18:19     ` Ted Zlatanov
2009-04-08 18:28       ` Tassilo Horn
2009-04-09  7:15         ` Tassilo Horn
2009-04-09 12:22           ` Tassilo Horn
2009-04-09 18:34           ` Tassilo Horn [this message]
2009-04-09 13:02       ` Ted Zlatanov
     [not found]       ` <86ws9uugj0.fsf__11476.5163431459$1239285119$gmane$org@lifelogs.com>
2009-04-09 14:40         ` David Engster

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=87y6u9y8u4.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.com \
    /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).