Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Garjola Dindi <garjola@garjola.net>
To: info-gnus-english@gnu.org
Subject: Re: Emacs resident looking for advice when Gnus blocks while fetching news
Date: Wed, 04 Dec 2019 22:04:00 +0100	[thread overview]
Message-ID: <87a787zttr.fsf@pc-117-162.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87v9qwumf9.fsf@ucl.ac.uk>

On Wed 04-Dec-2019 at 16:42:51 +01, "Fraga, Eric" <e.fraga@ucl.ac.uk> wrote: 
> On Wednesday,  4 Dec 2019 at 15:46, Garjola Dindi wrote:
>> One thing that bothers me is the fact that Gnus blocks my emacs when
>> fetching news, e-mails and RSS feeds (altough I use feed2imap for most
>> of my feeds).
>>
>> I understand that some emacs users use 2 different emacs instances, one
>
[..]
> 
> My solution now is to use group levels more smartly.  By default, "g" in
> the Group buffer only retrieves emails from my main server and that is
> quick.  If/when I know I have time, I retrieve from all servers by C-u 5
> g (say) or by M-g on individual lines in the Group buffer.
>
> You would need to play with gnus-activate-level in particular, I think.

Yes, I have set gnus-activate-level to 1 and level 1 contains only my
main inbox which is a nnmaildir (fed by offlineimap) and I use exactly
what you suggest to retrieve my other messages. I even have an idle
timer to retrieve everything when emacs is idle for a while.

The thing is that, even with that, Gnus is much slower than my
colleague’s mu4e and this is a bit frustrating.

Another thing I have found to make things slow is having an nnmaildir
with lots of messages. I therefore archive the oldest ones and use
mairix to index and query.

Maybe other methods than nnmaildir would be faster?

Anyway, thanks for the hints. If anything else I could do comes to mind,
I will be happy to try it.

G.


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2019-12-04 21:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 14:46 Garjola Dindi
2019-12-04 15:42 ` Fraga, Eric
2019-12-04 21:04   ` Garjola Dindi [this message]
2019-12-05 22:28     ` Fraga, Eric
2019-12-09 11:04       ` Garjola Dindi
2019-12-09 12:19         ` Fraga, Eric
2019-12-10 11:28         ` Emanuel Berg via info-gnus-english
2019-12-10 11:35           ` Emanuel Berg via info-gnus-english
2019-12-10 12:01             ` Emanuel Berg via info-gnus-english
2019-12-04 23:45 ` William Henderson
2019-12-09 11:02   ` Garjola Dindi

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=87a787zttr.fsf@pc-117-162.i-did-not-set--mail-host-address--so-tickle-me \
    --to=garjola@garjola.net \
    --cc=info-gnus-english@gnu.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).