From: Emanuel Berg <moasenwood@zoho.eu>
To: ding@gnus.org
Subject: Re: auto open servers?
Date: Sat, 12 Feb 2022 22:10:21 +0100 [thread overview]
Message-ID: <87o83bvlj6.fsf@zoho.eu> (raw)
In-Reply-To: <87mtiw2gsi.fsf@local.lan>
hput wrote:
>> Now it looks like this:
>>
>> (defun gnus-open-servers ()
>> (interactive)
>> (unless (get-buffer gnus-server-buffer)
>> (gnus-group-enter-server-mode) )
>> (with-current-buffer gnus-server-buffer
>> (gnus-server-open-all-servers)
>> (bury-buffer) )
>> (message "done") )
>
> Is that working for you?
Yep. Now it looks like this:
(defun gnus-open-servers (&optional silent)
(interactive)
(unless (get-buffer gnus-server-buffer)
(gnus-group-enter-server-mode) )
(with-current-buffer gnus-server-buffer
(gnus-server-open-all-servers)
(bury-buffer) )
(unless silent
(message "open") )) ; [1]
> I see no improvement running M-x
>
> gnus-open-servers <RET>
The improvement is, without it one server can be offline for
some reason, and it doesn't seem to reconnect, so when I do
`gnus-group-get-new-news' sometimes I think I'm not getting
any for a long time, then I think of checking *Server* and see
one or more if offline and get 50+ messages.
And sometimes I do actually get nothing, and I check the
*Server* buffer for no reason.
Since this, opening closed servers, is my only use case in the
*Server* buffer, and I always want them all open if possible,
I thought one would automate it. So now `gnus-open-servers'
happens before `gnus-group-get-new-news' ...
> Still get the busy sign for ages or maybe forever.
Sounds like that old bug or whatever it is ...
> Maybe I misunderstand this thread but I often see in server
> mode that server shows open but I get no action trying to
> send post or get new news, until I close server and
> then reopen.
The/a stuck process is perhaps killed that way, and restarted
it works again. Don't know why that happens (if so) tho ...
> Is it possible you can post something that combines both
> code snippets?
Sure, but opening a server that is closed makes sense, but
restarting it because it doesn't work otherwise is indicative
of a problem, that hasn't been solved ...
[1] https://dataswamp.org/~incal/emacs-init/gnus/group.el
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-02-12 21:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 1:28 Emanuel Berg
2022-01-24 8:39 ` Alberto Luaces
2022-01-24 9:40 ` Emanuel Berg
2022-01-24 10:06 ` Emanuel Berg
2022-01-24 10:46 ` Andreas Schwab
2022-01-25 21:28 ` Emanuel Berg
2022-01-25 21:35 ` Emanuel Berg
2022-02-12 16:25 ` hput
2022-02-12 20:24 ` Eric Abrahamsen
2022-02-12 21:11 ` Emanuel Berg
2022-02-12 21:31 ` Eric Abrahamsen
2022-02-12 21:38 ` Emanuel Berg
2022-02-23 16:07 ` hput
2022-02-23 16:19 ` hput
2022-02-23 16:44 ` Eric Abrahamsen
2022-02-26 6:29 ` Emanuel Berg
2022-02-26 6:34 ` Emanuel Berg
2022-02-12 21:10 ` Emanuel Berg [this message]
2022-02-13 13:29 ` hput
2022-02-13 22:46 ` Emanuel Berg
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=87o83bvlj6.fsf@zoho.eu \
--to=moasenwood@zoho.eu \
--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).