From: "J.P." <jp@neverwas.me>
To: 62044@debbugs.gnu.org
Cc: emacs-erc@gnu.org, xoddf2 <woddfellow2@gmail.com>
Subject: bug#62044: 30.0.50; ERC 5.5: Auto-reconnect is broken
Date: Fri, 27 Dec 2024 15:46:41 -0800 [thread overview]
Message-ID: <87v7v41yfy.fsf__35013.8660216302$1735343257$gmane$org@neverwas.me> (raw)
In-Reply-To: <87r05z7b1z.fsf@neverwas.me> (J. P.'s message of "Sun, 22 Dec 2024 11:49:28 -0800")
"J.P." <jp@neverwas.me> writes:
> "J.P." <jp@neverwas.me> writes:
>
>> A stop-gap solution for this issue was introduced in ERC 5.6 as
>> `erc-server-delayed-check-reconnect', a new function value for the
>> option `erc-server-reconnect-function'. There's since been some
>> criticism regarding its lack of discoverability, despite it featuring in
>> the Sample Configuration of ERC's manual. It's therefore been suggested
>> we favor the behavior it enables whenever possible by detecting
>> compatible values of `erc-server-connect-function'. Any false negatives
>> will hopefully only affect advanced users with nonstandard connectors.
>> The following patch tries to implement this. Feedback welcome.
>
> I ended up installing this (perhaps only temporarily) as
>
> https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=1c960bda
>
> At the end of the day, I still question the soundness of resorting to a
> protocol exchange to prove that the underlying transport is functioning
> properly. However, if no one complains in the next week or two, I'll
> close this with the release of 5.6.1.
I updated the behavior of `erc-server-delayed-check-reconnect' slightly
so it works without :nowait and reuses the probe connection if possible:
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=f5ebe47b
One potential problem with the latter approach might be a possible
server-enforced timeout if modules take too long to initialize. In any
case, if anyone finds these changes unsatisfactory, please say so.
Thanks.
prev parent reply other threads:[~2024-12-27 23:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 6:12 bug#62044: 30.0.50; ERC 5.5: Auto-reconnect is broken xoddf2
2023-03-08 7:56 ` J.P.
[not found] ` <87pm9jy8v7.fsf@neverwas.me>
2023-03-08 9:07 ` xoddf2
[not found] ` <87sfefr4qa.fsf@gmail.com>
2023-03-08 16:12 ` J.P.
[not found] ` <878rg7ql29.fsf@neverwas.me>
2023-03-09 2:22 ` J.P.
[not found] ` <87fsaepsso.fsf@neverwas.me>
2023-03-09 14:38 ` J.P.
[not found] ` <87lek6kn1b.fsf@neverwas.me>
2023-03-10 7:34 ` xoddf2
[not found] ` <87zg8lawlk.fsf@gmail.com>
2023-03-11 18:52 ` J.P.
[not found] ` <87v8j715om.fsf@neverwas.me>
2023-04-10 20:25 ` J.P.
2024-04-29 9:56 ` bug#62044: Status update? Alexis
2024-05-03 2:32 ` bug#62044: 30.0.50; ERC 5.5: Auto-reconnect is broken J.P.
[not found] ` <87wmoby69b.fsf@neverwas.me>
2024-05-09 6:13 ` Alexis
2024-12-02 3:50 ` J.P.
[not found] ` <871pyqd9qo.fsf@neverwas.me>
2024-12-22 19:49 ` J.P.
[not found] ` <87r05z7b1z.fsf@neverwas.me>
2024-12-27 23:46 ` J.P. [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='87v7v41yfy.fsf__35013.8660216302$1735343257$gmane$org@neverwas.me' \
--to=jp@neverwas.me \
--cc=62044@debbugs.gnu.org \
--cc=emacs-erc@gnu.org \
--cc=woddfellow2@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).