Gnus development mailing list
 help / color / mirror / Atom feed
From: David <de_bb@arcor.de>
To: ding@gnus.org
Subject: Re: released mairix backend nnmairix.el
Date: Sun, 07 Oct 2007 18:09:03 +0200	[thread overview]
Message-ID: <kzzlyuvrds.fsf@musil.physik3.gwdg.de> (raw)
In-Reply-To: <874ph3kezz.fsf@bzg.ath.cx>

Bastien <bzg@altern.org> writes:
> David <de_bb@arcor.de> writes:
>
>> The 'mfolder' setting in .mairixrc has no effect on nnmairix since it
>> always calls the mairix binary with the "-o" option for setting the
>> output folder manually on the command line (see also my reply to
>> Georg).
>
> Yes I know. My suggestion was to take care of this mairix-specific
> option in nnmairix.el and tell the nnmairix backend to use this
> directory as the default group.  Does that make sense?

Oh, I see. The problem is that the mairix installation may be on a
remote IMAP server where mairix is called via ssh (that's what I do), so
Gnus doesn't have access to the .mairixrc-file. But I will use the
directory in the server definition of the mail backend, as suggested by
Georg.

>I can browse the group nnmairix:default correctly, but there is still
>something weird with the fisrt displayed number of messages: it's sth
>like 45345 when it should be 143 (or so.) I guess it's related to the mh
>backend.

The problem is that mairix often doesn't produce consecutive article
numbers in the output folder when using mh. Since Gnus takes the
difference between the highest and lowest article number as the first
value for the numbers of articles, it is often way too high. When Gnus
actually enters the group, it should correct the number. I don't see how
to I could fix this problem in nnmairix.el (at least I'd say it's much
easier to fix this in mairix itself).

Regards,
David




  reply	other threads:[~2007-10-07 16:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 13:52 Getting rid of the zombies in dynamically created groups Georg C. F. Greve
2007-09-26 18:38 ` Reiner Steib
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 [this message]
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=kzzlyuvrds.fsf@musil.physik3.gwdg.de \
    --to=de_bb@arcor.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).