From: Richard Stallman <rms@gnu.org>
Subject: [rcyeske@gmail.com: Re: [deyke@comcast.net: rcirc fails to authenticate with bitlbee]]
Date: Tue, 25 Apr 2006 12:48:17 -0400 [thread overview]
Message-ID: <E1FYQi1-0001Ic-01@fencepost.gnu.org> (raw)
------- Start of forwarded message -------
Date: Mon, 24 Apr 2006 10:04:29 -0700
From: Ryan Yeske <rcyeske@gmail.com>
Cc: Dieter Deyke <deyke@comcast.net>
To: rms@gnu.org
In-reply-to: <E1FXzai-0006BK-0F@fencepost.gnu.org> (message from Richard
Stallman on Mon, 24 Apr 2006 07:50:56 -0400)
Subject: Re: [deyke@comcast.net: rcirc fails to authenticate with bitlbee]
X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO
autolearn=failed version=3.0.4
From: Richard Stallman <rms@gnu.org>
Reply-to: rms@gnu.org
Date: Mon, 24 Apr 2006 07:50:56 -0400
Do you want this installed?
No.
There is a control channel that the authentication string must be sent
to when talking to a bitlbee server. In BitlBee 1.0, the maintainers
switched from using #bitlbee to &bitlbee in order to differentiate it
from normal discussion channels. Around the same time, rcirc made
this change as well. This patch reverts back to using #bitlbee, which
is definitly wrong.
There is the problem that a number of people could still be using <1.0
versions of bitlbee, but my thinking was that they are pre-release
versions, and we shouldn't go to great lengths to work with them.
Perhaps the control channel could be pulled out into a defvar.
------- Start of forwarded message -------
From: Dieter Deyke <deyke@comcast.net>
To: emacs-pretest-bug@gnu.org
Date: Sun, 23 Apr 2006 08:38:18 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: rcirc fails to authenticate with bitlbee
X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO
autolearn=failed version=3.0.4
In GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600)
of 2006-04-20 on DEYKE1
X server distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
rcirc fails to authenticate with bitlbee. The error message is:
08:36 *** 401 &bitlbee Nick does not exist
The following patch fixes the problem for me:
*** old-rcirc.el Sun Apr 23 08:30:37 2006
- --- new-rcirc.el Sun Apr 23 08:31:03 2006
***************
*** 2140,2146 ****
((equal method 'bitlbee)
(rcirc-send-string
process
! (concat "PRIVMSG &bitlbee :identify " (car args))))
(t
(message "No %S authentication method defined"
method))))))))
- --- 2140,2146 ----
((equal method 'bitlbee)
(rcirc-send-string
process
! (concat "PRIVMSG #bitlbee :identify " (car args))))
(t
(message "No %S authentication method defined"
method))))))))
- --
Dieter Deyke
mailto:deyke@comcast.net mailto:deyke@gmx.net mailto:deyke@yahoo.com
Vs lbh pna ernq guvf, lbh unir jnl gbb zhpu gvzr.
_______________________________________________
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
------- End of forwarded message -------
------- End of forwarded message -------
reply other threads:[~2006-04-25 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1FYQi1-0001Ic-01@fencepost.gnu.org \
--to=rms@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.