all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: "J.P." <jp@neverwas.me>
Cc: Amin Bandali <bandali@gnu.org>, 50007@debbugs.gnu.org
Subject: bug#50007: 28.0.50; normalize logic surrounding erc-server-reconnecting
Date: Sun, 19 Sep 2021 09:36:14 -0700	[thread overview]
Message-ID: <CADwFkmkZ4kbqZqMWmhpprLAP+yGJsYMhgEbXg8PBvgHiR1GZkA@mail.gmail.com> (raw)
In-Reply-To: <87a6lojcij.fsf@neverwas.me> (J. P.'s message of "Wed, 11 Aug 2021 07:12:52 -0700")

"J.P." <jp@neverwas.me> writes:

> Tags: patch
>
> Knowing when we're reconnecting and having that logic be as sane and
> straightforward as possible is (IMO) a critical component of unraveling
> the buffer-association game I've been trying to drag everyone into.
>
> The existing approach is troublesome because it's basically inscrutable
> in the sense of being too difficult to sit down and reason through once
> session identities enter the fray (at least for a simpleton like me).
> And though the solution I'm proposing may seem underwhelming, it wasn't
> just intuited out of thin air but rather discovered with the backing of
> behavioral tests like the ones included in these patches [1]. Thanks.
>
>
> [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48598
>     https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49860

Copying in the ERC maintainer Amin Bandali here.

Amin, could you help review this patch?





  reply	other threads:[~2021-09-19 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 14:12 bug#50007: 28.0.50; normalize logic surrounding erc-server-reconnecting J.P.
2021-09-19 16:36 ` Stefan Kangas [this message]
2021-09-22  4:37   ` Amin Bandali
2021-11-06  2:16 ` Lars Ingebrigtsen
2021-11-06  8:49   ` J.P.
2021-11-06 18:13     ` Lars Ingebrigtsen
2021-11-06 22:02       ` J.P.

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=CADwFkmkZ4kbqZqMWmhpprLAP+yGJsYMhgEbXg8PBvgHiR1GZkA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=50007@debbugs.gnu.org \
    --cc=bandali@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.