all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Jean Louis <bugs@gnu.support>
Cc: 36714@debbugs.gnu.org
Subject: bug#36714: 27.0.50; Gnus nnmaildir taking long time to recursively visit sub-Maildirs
Date: Thu, 18 Jul 2019 12:00:25 -0700	[thread overview]
Message-ID: <87sgr32mnq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86ftn37cvz.fsf@protected.rcdrun.com> (Jean Louis's message of "Thu, 18 Jul 2019 14:20:16 +0200")

Jean Louis <bugs@gnu.support> writes:

> Hello,
>
> I am using Maildirs on my system. And I have 47682 various maildirs,
> each belong to one email in the ordered way like:
>
> ~/Maildir/email1@example.com
> ~/Maildir/email2@example.com
> ~/Maildir/email3@example.com
> ~/Maildir/email4@example.com
>
> and so on.
>
> Gnus offers nice interface and functions which I would like to use
> while reading email. Even though I like MH-E and Rmail more, they both
> do not offer Maildir support.
>
> I have made settings as following.
>
> '(gnus-secondary-select-methods
>    '((nnmaildir ""
> 	(directory "/home/data1/protected/Maildir/"))))
> 	
>  '(gnus-select-method '(nnimap "my.imap"))
>
> Now, I do not need to susbcribe to 47682 Maildirs at once, as under
> ~/Maildir I have cur, new, tmp and that is the Maildir I would like to
> read as only one.
>
> However, after setting the above, Gnus started doing something since
> yesterday, and I still do not know what it is, it is maybe indexing or
> setting up something, I do not know, process is still running for many
> hours.
>
> I think that this is bug.
>
> What I think is that Gnus is now recursively visiting all Maildirs
> instead of using just the main one.

I think you're right, and in a sense it is definitely a bug, but a lot
of people have run into this and I've seen some saying "there's not much
to be done". So that didn't sound very encouraging.

Could you do M-x toggle-debug-on-quit, start up Gnus, let it hang for a
bit, then do "C-g" and post the resulting backtrace here? It's fairly
obvious what's going on, but it would be good to see the specifics.

The nnmaildir servers keep track of their directory modtime, which is
both set and read only once, in `nnmaildir-request-scan'. So at least it
should be fairly easy to see what's happening there. Gnus doesn't save
the modtimes, though -- perhaps a potential solution could involve
saving the maildir modtimes in newsrc.eld.

> And my other question is, is there a way to quickly access
> Maildir/email2@example.com by using Gnus? Some function maybe to just
> write the email address or fetch it from database, and to open the
> Maildir with nnmaildir?

I'm not entirely sure what you mean here, but one suggestion I have is
to create four different nnmaildir select methods, one for each of your
email addresses. I think that's how Gnus is expecting this sort of thing
to be set up, and it might make it easier for you to access, as well.

Eric





  reply	other threads:[~2019-07-18 19:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 12:20 bug#36714: 27.0.50; Gnus nnmaildir taking long time to recursively visit sub-Maildirs Jean Louis
2019-07-18 19:00 ` Eric Abrahamsen [this message]
2019-07-18 19:43   ` Jean Louis
2019-07-18 20:03     ` Eric Abrahamsen
2019-07-18 20:48       ` Jean Louis
2019-07-19  0:27         ` Eric Abrahamsen
2019-07-19  6:15           ` Jean Louis
2019-07-19 17:23             ` Eric Abrahamsen
2019-07-19 17:31               ` Jean Louis
2019-07-19 18:49                 ` Eric Abrahamsen
2019-07-22  8:44               ` Jean Louis
2019-07-22 17:40                 ` Eric Abrahamsen
2019-07-23  7:30                   ` Jean Louis
2019-07-24 18:18                     ` Eric Abrahamsen
2019-07-24 18:25                       ` Eric Abrahamsen
2019-07-22  8:34           ` Basil L. Contovounesios
2019-07-22 17:21             ` Eric Abrahamsen
2019-07-22 17:41             ` Eric Abrahamsen
2019-07-23  7:37               ` Jean Louis

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=87sgr32mnq.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=36714@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.