From: Lars Ingebrigtsen <larsi@gnus.org>
To: Deniz Dogan <deniz.a.m.dogan@gmail.com>
Cc: 6795@debbugs.gnu.org
Subject: bug#6795: rcirc: ERR_NICKNAMEINUSE causes infinite loop under certain circumstances
Date: Tue, 08 Dec 2020 18:23:06 +0100 [thread overview]
Message-ID: <87mtyodxfp.fsf@gnus.org> (raw)
In-Reply-To: <AANLkTi=e+exmg2w=fD0yLCz_MQv8NafYq=Mq44GTuqR9@mail.gmail.com> (Deniz Dogan's message of "Wed, 4 Aug 2010 19:55:21 +0200")
Deniz Dogan <deniz.a.m.dogan@gmail.com> writes:
> Currently rcirc-handler-433 (ERR_NICKNAMEINUSE) tries to "uniquify"
> the nickname the user tried to use by appeding a ` to the requested
> nickname. However, if the length of the requested nickname is as long
> as or longer than the maximum allowed length on the server, the
> "uniquification" will not work resulting in an attempt to switch to
> the same nickname that caused the error in the first place:
>
> Example:
> /nick superlongnickname
> *** 433 superlongn Nickname is already in use.
>
> Here the IRC server truncates the requested nickname to "superlongn"
> which is already taken and then it tries to change to
> "superlongnickname`" which of course will also be truncated to
> "superlongn". Hence, something like this will be printed in the server
> buffer:
>
> *** 433 superlongn Nickname is already in use.
> *** 433 superlongn Nickname is already in use.
> *** 433 superlongn Nickname is already in use.
> *** 433 superlongn Nickname is already in use.
This should now be fixed in Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-12-08 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 17:55 bug#6795: rcirc: ERR_NICKNAMEINUSE causes infinite loop under certain circumstances Deniz Dogan
2020-12-08 17:23 ` Lars Ingebrigtsen [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=87mtyodxfp.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=6795@debbugs.gnu.org \
--cc=deniz.a.m.dogan@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 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.