Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: William Henderson <wmhenderson@freeshell.org>
To: info-gnus-english@gnu.org
Cc: info-gnus-english@gnu.org
Subject: Re: Emacs resident looking for advice when Gnus blocks while fetching news
Date: Wed, 04 Dec 2019 16:45:26 -0700	[thread overview]
Message-ID: <87fthzvend.fsf@sdf.org> (raw)
In-Reply-To: <87h82gw3lb.fsf@pc-117-162.i-did-not-set--mail-host-address--so-tickle-me>

Garjola Dindi <garjola@garjola.net> writes:

> Hi,
>
> I have been using Gnus for more than a decade now and I am still
> learning useful things to improve my workflow.
>
> Since I live in emacs, my use of Gnus is highly integrated with org-mode
> (capture from Gnus, jump to messages from org-mode links, etc.)
>
> 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
> for Gnus and another one for the rest. In my case, I am not sure that
> that this would solve my issues cleanly because the integration
> mentioned above: I may and having conflicts if the same file is open by
> both instances.
>
> I am sure I am not the only one in this situation and I am therefore
> looking for advice on how to solve or at least enhance the situation.

OK, so this is my set up

[START FLUXBOX STARTUP INCLUSION]
My ~/.fluxbox/startup includes
 fetchmail -F -d 900 -f ~/.fetchmailrc &
 anymail &
[/START FLUXBOX STARTUP INCLUSION]


[START HOME DIRECTORY INCLUSION:
~/ contains .fetchmailrc
----
poll POPSERVER1 proto pop3 
   user USER1 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER2 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER3 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER4 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER5 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER6 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER7 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here
poll IMAPSERVER1 proto imap
   user USER8 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here   
poll POPSERVER2 proto pop3
   user USER9  password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER10 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER11 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER12 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER13 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER14 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER15 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER16 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER17 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER18 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER19 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here
poll POPSERVER3 proto pop3
   user USER20 password "velovelo" is MYLINUXSYSTEMUSERNAME here
[/START HOME DIRECTORY INCLUSION]


[START ROOT INCLUSION]
/root CONTAINS .fetchmailrc
----
poll POPSERVER1 proto pop3 
   user USER1 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER2 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER3 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER4 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER5 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER6 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER7 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here
poll IMAPSERVER1 proto imap
   user USER8 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here   
poll POPSERVER2 proto pop3
   user USER9  password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER10 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER11 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER12 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER13 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER14 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER15 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER16 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER17 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER18 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here;
   user USER19 password "PASSWORD" is MYLINUXSYSTEMUSERNAME here
poll POPSERVER3 proto pop3
   user USER20 password "velovelo" is MYLINUXSYSTEMUSERNAME here
[/START ROOT INCLUSION

The .fetchmailrc in /root permits me to occasionally visually see what
is happening and if necessary log in webmail to a particualar server to
fic any snags.

You might get some comments about using "F" when starting fetchmail, but
this works for me.

The above dumps your emails into /var/spool/mail/MYLINUXSYSTEMUSERNAME

It then needs to be broght into GNUS via:
[1] "g"
[2] having in  ~/.gnus the following:
;; AUTOMATICALLY CHECK MAILPERIODICALLY
(add-hook 'gnus-startup-hook
  '(lambda ()
     (gnus-demon-init)
     (setq gnus-demon-timestep 1)  ;; each timestep is 1 second
     ;; Check for new mail every 300 timesteps (5 minute)
     (gnus-demon-add-handler 'gnus-demon-scan-news 300 t)
     (gnus-demon-add-handler 'gnus-demon-scan-mail 300 t)

     ;; Don't crash gnus if disconnected
     (defadvice gnus-demon-scan-news (around gnus-demon-timeout activate)
       "Timeout for Gnus."
       (with-timeout
       (120 (message "Gnus timed out."))
     ad-do-it))))

[ANYMAIL]
IN /usr/local/bin/anymail
----
filename=/var/spool/mail/inconnu
maxsize=0
filesize=$(stat -c%s "$filename")
if (( filesize > maxsize )); then
        xmessage -nearmouse "inconnu HAS MAIL"
else
        xmessage -nearmouse "NO MAIL for inconnu"
fi
[/ANYMAIL]

Hopefully the forgoing might be of some assistance to you.

You can then start other emacs functions with M-x (Like erc, editor,
etc)

ANYMAIL will tell you via xmessage if you have any mail.

-- 
William Henderson
aka Slackrat
http://billh.sdf.org/slackware.jpg
9HS5203 on HamSphere

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

  parent reply	other threads:[~2019-12-04 23:45 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
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 [this message]
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=87fthzvend.fsf@sdf.org \
    --to=wmhenderson@freeshell.org \
    --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).