From: Tassilo Horn <tsdh@gnu.org>
To: Oleksandr Gavenko <gavenkoa@gmail.com>
Cc: ding@gnus.org
Subject: Re: Features that make you love Gnus?
Date: Fri, 21 Sep 2012 08:35:51 +0200 [thread overview]
Message-ID: <87r4pv6fy0.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <876278tinr.fsf@gavenkoa.example.com> (Oleksandr Gavenko's message of "Fri, 21 Sep 2012 01:48:40 +0300")
Oleksandr Gavenko <gavenkoa@gmail.com> writes:
> But I notice problems behind Gnus that have no solution known to me:
>
> * Blocking Emacs during Gnus loading. news.rsdn.ru server have
> special timing policy for access to their groups, so *Group* buffer
> can unfreeze after 30 sec...
>
> Gnus Agent don't help with this issue I think...
Yes, right now Gnus blocks when getting new news/mail. But some people
are experimenting with asynchronously performing such longrunning ops
(see async.el from John Wiegley), and there's Tom Tromey experimenting
with threads in emacs. So the situation may become better in the middle
term.
> I look to INN and Leafnode solutions, but don't understand how
> Emacs will be send message back to NNTP...
It'll deliver the posting to your local leafnode, and that propagates it
back to your "real" news server.
> * Notification when someone replay to me or articles marked as
> ticked/dormant (!/?). I expect that Gnus periodically reloads all
> groups for which I subscribed (and posted to or have ticked/dormant
> articles) and scans for replays below my messages based on
> Message-Id.
You could use gnus-notifications to get notifications on new news/mail.
And you could use scoring so that replies to your messages get a very
high score, and then sort according to score.
> I ask question:
>
> Subject: Notifying me to read message from selected groups for
> new messages only if score greater then N.
Oh, sounds about what I've just suggested. But I think
gnus-notifications currently notifies regardless of score or other
predicates. Probably, this cannot be done easily, because I think
scores are computed not until you enter a summary buffer which it
doesn't do. Julien will know the definitive answer.
Bye,
Tassilo
next prev parent reply other threads:[~2012-09-21 6:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 13:48 Kyle Sexton
2012-09-20 22:48 ` Oleksandr Gavenko
2012-09-21 6:35 ` Tassilo Horn [this message]
2012-09-23 21:34 ` Oleksandr Gavenko
2012-09-24 6:47 ` Tassilo Horn
2012-09-21 1:11 ` Mark Simpson
2012-09-23 21:38 ` Oleksandr Gavenko
2012-09-23 23:59 ` Mark Simpson
2012-09-21 6:50 ` Tassilo Horn
2012-09-21 13:16 ` Erik Colson
2012-09-21 18:23 ` Sivaram Neelakantan
2012-09-21 18:56 ` Tassilo Horn
2012-09-23 21:42 ` Oleksandr Gavenko
2012-09-24 6:52 ` Tassilo Horn
2012-09-24 8:22 ` Andreas Schwab
2012-09-21 13:23 ` Julien Danjou
2012-09-22 17:39 ` Adam Sjøgren
2012-09-25 13:20 ` Malcolm Purvis
2012-09-24 7:26 ` Eric Abrahamsen
2012-09-24 12:30 ` Adam Sjøgren
2012-09-26 6:26 ` Eric Abrahamsen
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=87r4pv6fy0.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=gavenkoa@gmail.com \
/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).