Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Cc: Magnus Henoch <mange@freemail.hu>
Subject: change in open-tls-stream, jabber does not work any longer
Date: Thu, 17 Jul 2008 13:05:19 +0200	[thread overview]
Message-ID: <87vdz4ydn4.fsf@mat.ucm.es> (raw)

Hello

While jabber (emacs-jabber-0.7.1) worked fine for me in ngnus 0.6, 
it stopped working with ngnus.0.10, the reason seems to be a change in
the function 
  open-tls-stream

I attach the error message and ask what could I do?


Debugger entered--Lisp error: (error "Selecting deleted or non-existent buffer")
  open-tls-stream("jabber" " *-jabber-process-*" "talk.google.com" 5223)
  jabber-ssl-connect()
  jabber-connect()
  (lambda nil (interactive) (jabber-connect) (switch-to-buffer "*-jabber-*"))()
  call-interactively(jabber)
  recursive-edit()
  byte-code("..." [buffer-read-only noninteractive debugger-buffer middlestart debugger-args debugger-batch-max-lines pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output] 3)
  debug(error (error "No recursive edit is in progress"))
  signal(error ("No recursive edit is in progress"))
  cerror("No recursive edit is in progress")
  apply(cerror "No recursive edit is in progress" nil)
  error("No recursive edit is in progress")
  #<compiled-function nil "...(15)" [recursion-depth 0 throw exit nil error "No recursive edit is in progress"] 3 679460 nil>()
  call-interactively(exit-recursive-edit)




             reply	other threads:[~2008-07-17 11:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 11:05 Uwe Brauer [this message]
2008-07-17 12:13 ` Katsumi Yamaoka
2008-07-17 12:37   ` Uwe Brauer
2008-07-18  0:25     ` Katsumi Yamaoka
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=87vdz4ydn4.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=ding@gnus.org \
    --cc=mange@freemail.hu \
    /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).