unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: xoddf2 <woddfellow2@gmail.com>
To: "J.P." <jp@neverwas.me>
Cc: emacs-erc@gnu.org, 62044@debbugs.gnu.org
Subject: bug#62044: 30.0.50; ERC 5.5: Auto-reconnect is broken
Date: Thu, 09 Mar 2023 23:34:15 -0800	[thread overview]
Message-ID: <87zg8lawlk.fsf__13826.4502560318$1678433736$gmane$org@gmail.com> (raw)
In-Reply-To: <87lek6kn1b.fsf@neverwas.me>


J.P. writes:

> [...]
>
> I've improved upon this further (v3 attached) by adding a housekeeping
> task to monitor the initial server process from creation. Such a move
> may be regrettable because it adds yet more complexity to the already
> dizzying auto-reconnect landscape. However, I couldn't find a suitable
> way to cover common process errors that aren't presented to the sentinel
> but still need to engage the reconnect logic.
>
> If this leads to a futile game of whack-a-mole, we'll obviously need to
> try a different approach. But if we do more-or-less build on what I've
> got so far, we'll definitely need to ensure it agrees with 27 and 28
> before spending serious energy on refinement and tests.
>
> Thanks.

Version 3 of the patch works, both with an otherwise unconfigured ERC
and with a full configuration connecting to my bouncer.

I used this setting in both cases:
(setq erc-server-reconnect-function 'erc-server-delayed-check-reconnect)

The first 2 versions did not work at all.

Thanks
-- 
xoddf2 | https://wlair.us.to/ | PGP: 20EB90D3





  parent reply	other threads:[~2023-03-10  7:34 UTC|newest]

Thread overview: 12+ 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 [this message]
     [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

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='87zg8lawlk.fsf__13826.4502560318$1678433736$gmane$org@gmail.com' \
    --to=woddfellow2@gmail.com \
    --cc=62044@debbugs.gnu.org \
    --cc=emacs-erc@gnu.org \
    --cc=jp@neverwas.me \
    /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).