jabber.el

> Can anybody use emacs-jabber with Emacs 22.2?

I am not 100 percent sure but I think I did once. Now I use CVS Emacs,
version 23.0.60.2 to be exact. Have you tried starting with emacs -Q
and only loading emacs-jabber after that?

On 4/17/08, Milan Zamazal <pdm@...> wrote:
> Can anybody use emacs-jabber with Emacs 22.2?  After I upgraded Emacs
>  (and perhaps some other things) from 22.1 to 22.2, I can't connect to my
>  server anymore.  I receive the following message on each `M-x
>  jabber-connect' attempt:
>
>   Jabber connection lost: `exited abnormally with code 1
>   '
>
>  Another user, who uses TLS connections, has reported that after
>  upgrading to Emacs 22.2 he receives the following error on
>  jabber-connect:
>
>   Debugger entered--Lisp error: (error "No buffer named  *-jabber-process-*")
>     open-tls-stream("jabber" " *-jabber-process-*" "talk.google.com" 5223)
>     jabber-ssl-connect()
>     jabber-connect()
>     eval((jabber-connect))
>     eval-last-sexp-1(nil)
>     eval-last-sexp(nil)
>     call-interactively(eval-last-sexp)
>
>  Creating the buffer ` *-jabber-process-*' manually remedies the problem
>  for him.

This was easy one:

-----BEGIN PATCH-----
--- jabber-conn.el.orig 2006-04-23 18:09:56.000000000 +0300
+++ jabber-conn.el      2008-04-21 21:40:34.694079414 +0300
@@ -132,7 +132,7 @@
            (when (setq *jabber-connection*
                        (open-network-stream
                         "jabber"
-                        jabber-process-buffer
+                        (get-buffer-create jabber-process-buffer)
                         (car target)
                         (cdr target)))
              (throw 'connected t))
@@ -165,7 +165,7 @@
       (setq *jabber-connection*
            (funcall connect-function
                     "jabber"
-                    jabber-process-buffer
+                    (get-buffer-create jabber-process-buffer)
                     (or jabber-network-server jabber-server)
                     (or jabber-port 5223)))))

-----END PATCH-----

Step by step:
; (if (> expertise enough) (ignore))
  * copy-paste the patch to file `/tmp/jabber-conn.el.diff'
  * cd SRC_DIR  # the one with `jabber-conn.el'
    (SRC_DIR=/usr/share/emacs/site-lisp/emacs-jabber on Debian)
  * patch < /tmp/jabber-conn.el.diff
  * emacs -batch -f batch-byte-compile jabber-conn.el
  * mv jabber-conn.elc DEST_DIR
    (DEST_DIR=/usr/share/emacs22/site-lisp/emacs-jabber on Debian)

Have fun!

-- 
vvv

>>>>> "VVV" == Valery V Vorotyntsev <valery.vv@...> writes:

    >> Debugger entered--Lisp error: (error "No buffer named  *-jabber-process-*")
    >> open-tls-stream("jabber" " *-jabber-process-*" "talk.google.com" 5223)
    >> jabber-ssl-connect()
    >> jabber-connect()
    >> eval((jabber-connect))
    >> eval-last-sexp-1(nil)
    >> eval-last-sexp(nil)
    >> call-interactively(eval-last-sexp)
    >> 
    >> Creating the buffer ` *-jabber-process-*' manually remedies the problem
    >> for him.

    VVV> This was easy one:

[...]

    VVV> -                        jabber-process-buffer
    VVV> +                        (get-buffer-create jabber-process-buffer)

I see.  Indeed, open-tls-stream requires that the process buffer exists
in advance.  In case of open-network-stream it's not necessary.  So I'll
apply the fix to the Debian package.  Thanks!

BTW, as for my own connection problem, it was just mess in my settings,
so please forget about that part.

Regards,

Milan Zamazal