all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@redhat.com>
To: 54087@debbugs.gnu.org
Subject: bug#54087: 28.0.91; rcirc: irc.gnome reg timeout; reconnects after quit
Date: Wed, 23 Feb 2022 07:03:50 -0500	[thread overview]
Message-ID: <fa0ee651-7a7e-a70b-eb10-dc0652f73324@redhat.com> (raw)
In-Reply-To: <b08a1798-4f25-5d74-32e3-057720fe4a30@redhat.com>

FWIW, I'm hacking around the bug for now by advising a function, and it 
seems to be working for both irc.gnome.org and my company IRC server. So 
the trailing space may have been the only issue blocking registration 
completion.


(defun kr-munge-args--rcirc-handler-CAP (all-args)
   (let ((cap-args (nth 2 all-args)))
     (while cap-args
       (if (string-match " +$" (car cap-args))
       (setcar cap-args (substring (car cap-args)
                       0 (match-beginning 0))))
       (setq cap-args (cdr cap-args))))
   all-args)

(if (version= emacs-version "28.0.91")
     (advice-add 'rcirc-handler-CAP
         :filter-args #'kr-munge-args--rcirc-handler-CAP))


So, to recap:

1) trailing space in CAP reply breaks registration

2) /quit triggers reconnect (if reconnection enabled)

3) name resolution failure not reported, just a vague connection failure

The parallel connection management seems to work nicely. (I could wish 
for separate threads so that when, say, Gnus ties up the main thread for 
several minutes trying to connect to a server that's down, the IRC 
servers don't decide my client has stopped responding. At least, I would 
hope other threads can run at that point.) I'll see if I run into any 
other problems in the next few days...

Ken






      reply	other threads:[~2022-02-23 12:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 11:12 bug#54087: 28.0.91; rcirc: irc.gnome reg timeout; reconnects after /quit Ken Raeburn
2022-02-22  8:44 ` bug#54087: 28.0.91; rcirc: irc.gnome reg timeout; reconnects after quit Ken Raeburn
2022-02-23  0:35   ` Ken Raeburn
2022-02-23 12:03     ` Ken Raeburn [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa0ee651-7a7e-a70b-eb10-dc0652f73324@redhat.com \
    --to=raeburn@redhat.com \
    --cc=54087@debbugs.gnu.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.
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.