From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: ding@gnus.org, Magnus Henoch <mange@freemail.hu>
Subject: Re: change in open-tls-stream, jabber does not work any longer
Date: Fri, 18 Jul 2008 09:25:50 +0900 [thread overview]
Message-ID: <b4mzloghwc1.fsf@jpl.org> (raw)
In-Reply-To: <87y740znx5.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
>>>>> Uwe Brauer wrote:
>> Performing jabber again after loading tls.el (not tls.elc) will
>> make the cause of the problem more clearer. (I'm ignorant of
>> jabber though.)
> I am not so sure, after loading the file and debug-on-error t
> I obtain
> --8<------------------------schnipp------------------------->8---
> Debugger entered--Lisp error: (error "Selecting deleted or non-existent buffer")
> set-buffer(" *-jabber-process-*")
> (save-current-buffer (set-buffer buffer) (message "Opening TLS connectio...
> (with-current-buffer buffer (message "Opening TLS connection to `%s'..."...
[...]
> open-tls-stream("jabber" " *-jabber-process-*" "talk.google.com" 5223)
> jabber-ssl-connect()
I see. The workaround is:
[-- Attachment #2: Type: application/emacs-lisp, Size: 311 bytes --]
[-- Attachment #3: Type: text/plain, Size: 515 bytes --]
emacs-jabber-0.7.1 passes the buffer name (that is only a string,
has not been created yet) as the second argument to `open-tls-stream'.
The reason the former `open-tls-stream' worked is that it directly
passed the buffer name to `start-process', that creates the buffer
even if it is only a string. I believe the present one should be
fixed because it is mentioned in the doc-string:
BUFFER is the buffer (or buffer name) to associate with the process.
^^^^^^^^^^^^^^^^
I'll do it later...
next prev parent reply other threads:[~2008-07-18 0:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 11:05 Uwe Brauer
2008-07-17 12:13 ` Katsumi Yamaoka
2008-07-17 12:37 ` Uwe Brauer
2008-07-18 0:25 ` Katsumi Yamaoka [this message]
2008-07-30 9:06 ` Uwe Brauer
2008-07-30 10:06 ` Katsumi Yamaoka
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=b4mzloghwc1.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=mange@freemail.hu \
--cc=oub@mat.ucm.es \
/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.
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 NNTP newsgroup(s).