Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexander Baier <lexi.baier@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Create a group from a list of message-ids
Date: Thu, 28 Nov 2013 13:02:03 +0100	[thread overview]
Message-ID: <87zjooivk4.fsf@gmail.com> (raw)
In-Reply-To: <87siujyfh0.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 26 Nov 2013 11:06:03 +0700")

On 13-11-26 05:06 Eric Abrahamsen wrote:
> Frank Terbeck <ft@bewatermyfriend.org> writes:
>
>> Eric Abrahamsen wrote:
>> [...]
>>> It also comes with its own tagging structure and all kinds of stuff I
>>> don't use. The superfluity bugs me a little, but the searching is nice
>>> enough that it doesn't matter. A nnir plugin for notmuch might actually
>>> be nice.
>>
>> Actually, at least in the git version of gnus, ‘nnir’ seems to feature
>> support for ‘notmuch’ (ie. there is a defcustom ‘nnir-notmuch-program’
>> and a defun ‘nnir-run-notmuch’).
>>
>> Since ‘mu’ seems to work fairly similarly to notmuch, I would guess
>> that, this part would serve as a source for ideas for ‘mu’-integration.
>>
>> Regards, Frank
>
> Thanks to both of you for pointing that out! I had no idea that was
> there, but would definitely prefer using a more gnus-y interface. I set
> it up like so:
>
> (setq nnir-method-default-engines  '((nnimap . notmuch) (nntp . gmane)))
>
> And gave it a shot.
>
> It didn't work for me for two reasons. I have several different imap
> servers, all run through dovecot with a maildir structure. They're all
> under ~/.mail, like ~/.mail/acc1 ~/mail/acc2 etc. That means
> nnir-notmuch-remove-prefix has to be set to an appropriate value for
> each server, which you can do with server parameters. But that means you
> can only search one server at a time (which I guess you'd do by putting
> a notmuch-group key into the query? I don't even know how to do that).
> That isn't really what I want -- I'd like to search all my mail at once.
> And even if I had to do it server by server, it seems like
> `nnir-run-notmuch' should be able to figure out how to filter to that
> server by itself...
>
> The second problem was the maildir structure. I specify maildir through
> the nnimap-shell-program parameter, which looks like:
>
> /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/.mail/acc1/:LAYOUT=fs
>
> `nnir-compose-result' munges results differently depending on whether
> they're maildir or not, but it only determines that by checking
> (gnus-group-server server) for the nnmaildir string. I'd need to change
> that, I guess by putting more thorough checking in `nnir-run-notmuch',
> `nnir-run-namazu', and `nnir-run-swish++', which would then pass a flag
> to `nnir-compose-results'.
>
> Lastly, a notmuch result in my case looks like this:
>
> /home/eric/.mail/pr/[Gmail]/Sent Mail/cur/1384510308.M437592P10993.pellet,S=3672,W=3728:2,S
>
> Which would, if the above problems were fixed, turn into a result that looks like
> ["nnimap+PR:[Gmail].Sent Mail" "1384510308.M437592P10993.pellet"]. The problem
> there is that the slash between [Gmail] and Sent Mail (which really is
> a filesystem separator, because I've used LAYOUT=fs) gets turned into a
> dot, when it's actually supposed to remain a slash. That's probably my
> fault for using LAYOUT=fs, and it would be ugly to put a special-case
> check for that in nnir.el
>
> Ahem, so... Please consider that mostly notes to self. If you're not
> using dovecot with a maildir layout, this probably won't be an issue.
>
> I'd be happy to provide a patch for more thorough checking for maildir
> structure, but I probably won't use this anyway, because I don't want to
> be restricted to searching one server at a time.
>
> All for now,
> Eric
>
Hi Eric,

I am digging this up again, as I had some time to look at this myself
and maybe have an idea of how to tackle this problem.

Now, as I see it, the thing preventing us from searching multiple
servers is the fact that nnir-compose-result might be passed a server
that does not fit to the matched article as this may come from a
different server.  So I think, solving this problem is "just" a matter
of teaching nnir-compose-result to correct the server it is passed in
case it does not fit to the matched article.  For nnir-compose-result to
be able to so we need to tell it how to extract the server from the
dirnam parameter.  The question is, how do we tell nnir-compose-result
this?  Do you have any ideas on this?

Regards,
-- 
 Alexander Baier

PS: After writing this I am not exactly sure if I am just rehashing your
point(s), in case that is true I apologize.



  parent reply	other threads:[~2013-11-28 12:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 11:50 Alexander Baier
2013-11-25  2:02 ` Dave Goldberg
2013-11-25  8:52   ` Alexander Baier
2013-11-25  8:58     ` Frank Terbeck
2013-11-25  9:11       ` Alexander Baier
2013-11-25  9:01     ` Eric Abrahamsen
2013-11-25  9:13       ` Alexander Baier
2013-11-25 13:20         ` Eric Abrahamsen
2013-11-25 14:08           ` Alexander Baier
2013-11-25 15:26             ` Eric Abrahamsen
2013-11-25 15:44               ` Frank Terbeck
2013-11-26  4:06                 ` Eric Abrahamsen
2013-11-27  5:16                   ` Eric Abrahamsen
2013-11-27  7:34                     ` Alexander Baier
2013-11-27  8:10                       ` Eric Abrahamsen
2013-11-27  8:22                         ` Alexander Baier
2013-11-28 12:02                   ` Alexander Baier [this message]
2013-11-29  3:41                     ` Eric Abrahamsen
2013-11-30 18:56                       ` Alexander Baier
2013-11-25 16:11               ` Alexander Baier
2013-11-25  9:28   ` Pedro Silva
2013-11-25  9:44     ` Alexander Baier

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=87zjooivk4.fsf@gmail.com \
    --to=lexi.baier@gmail.com \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).