unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Ken Raeburn <raeburn@redhat.com>, 45872@debbugs.gnu.org
Subject: bug#45872: 27.1; rcirc nick tracking
Date: Fri, 23 Jul 2021 12:02:12 +0000	[thread overview]
Message-ID: <87czr99r23.fsf@posteo.net> (raw)
In-Reply-To: <87im11dzcz.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 23 Jul 2021 13:49:16 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Ken Raeburn <raeburn@redhat.com> writes:
>
>> One of my IRC contacts uses frequent nick changes to indicate away
>> status, e.g., "johnsmith" when available, "johnsmith|away",
>> "johnsmith|vacation", whatever. I've noticed that sometimes rcirc will
>> fail to rename the buffer used for private messages between us, and so
>> I'll wind up with a buffer "johnsmith|away" showing something along the
>> lines of:
>>
>>   ... *** johnsmith NICK johnsmith|away
>>   ... *** johnsmith|away NICK johnsmith
>>
>> but the buffer won't have been renamed back to "johnsmith@<server>",

Do you have some idea in what cases the buffer is not renamed?  In
principle, the NICK handler (rcirc-handler-NICK) should handle this
case, but there might be issues if you disconnect and reconnect.

>> and if I try sending him a message, it'll try sending to
>> johnsmith|away and will fail.  I can use "/msg johnsmith...", or he
>> can send messages to me, and a new buffer will be created.

This hasn't been fixed yet, but I am intending to do so.

> rcirc has gotten a lot of fixes in Emacs 28, but I'm not sure whether
> this is one of the things that have been fixed.  I've added Philip to
> the CCs; he'll probably know.  :-)

-- 
	Philip Kaludercic





  reply	other threads:[~2021-07-23 12:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 19:42 bug#45872: 27.1; rcirc nick tracking Ken Raeburn
2021-07-23 11:49 ` Lars Ingebrigtsen
2021-07-23 12:02   ` Philip Kaludercic [this message]
2021-07-23 18:07     ` Ken Raeburn
2021-07-23 20:33       ` Ken Raeburn
2021-07-24 14:56       ` Philip Kaludercic
2021-07-26 21:46         ` Ken Raeburn
2021-07-27  8:22           ` Philip Kaludercic
2022-03-17 18:55             ` Ken Raeburn
2022-06-07 13:30               ` Lars Ingebrigtsen
2022-07-05 19:06                 ` Lars Ingebrigtsen

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=87czr99r23.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=45872@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=raeburn@redhat.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).