1 #+TITLE: jabber.el - an XMPP client for Emacs
2 #+DESCRIPTION: Documentation
3 #+startup: inlineimages
7 :CUSTOM_ID: explanation
9 jabber.el is an [[http://xmpp.org][XMPP]] client for Emacs. XMPP (also known as 'Jabber') is an IETF-standard federated instant messaging protocol.
11 To try it out, see the [[#installation][install instructions]].
14 + [[https://codeberg.org/emacs-jabber/emacs-jabber/][project page]]
15 + chat: [[xmpp:emacs@salas.suchat.org?join][xmpp:emacs@salas.suchat.org?join]] (general Emacs and jabber.el talk)
16 + chat: xmpp:jabber-el@conference.hmm.st?join (jabber.el developement)
19 + [[http://sourceforge.net/projects/emacs-jabber][project page]]
20 + [[http://emacs-jabber.sourceforge.net][home page]]
21 + [[http://www.emacswiki.org/cgi-bin/wiki/JabberEl][wiki page]]
23 * http://lists.sourceforge.net/lists/listinfo/emacs-jabber-general
24 * http://dir.gmane.org/gmane.emacs.jabber.general
25 + chat: jabber.el@conference.jabber.se and emacs@conference.jabber.ru (Russian, English)
27 ** Differences from [[https://github.com/legoscia/emacs-jabber][upstream]]
29 :CUSTOM_ID: upstream-differences
31 1. (WIP) Support for [[https://xmpp.org/extensions/xep-0363.html][XEP-0363: HTTP File Upload]]
32 2. Support for [[https://xmpp.org/extensions/xep-0280.html][XEP-0280: Message Carbons]]
33 3. Use of the deprecated =cl= library is almost completely replaced with =cl-lib=
34 4. Build system changed from Autotools to a =Makefile=
35 5. Lots of cleanup by addressing =checkdoc= and byte-compiler warnings - addition/improvement of docstrings, function/variable declarations, etc
39 :CUSTOM_ID: requirements
41 jabber.el runs on GNU Emacs 27.1 or later.
43 The file hexrgb.el (http://www.emacswiki.org/emacs/hexrgb.el) used to be required for the MUC nick coloring feature. However, the code depending on it has been reworked to instead use the =color.el= library, which is part of Emacs.
45 ** Encrypted connections
47 :CUSTOM_ID: encrypted-connections
49 Many Jabber servers require encrypted connections, and even if yours doesn't it may be good idea. To get an encrypted connection, the most convenient option is to use GNU Emacs 24 with GnuTLS support compiled in. You can check whether you have that by typing:
51 : M-: (gnutls-available-p)
53 If that commands shows =t= in the echo area, then you have working GnuTLS support. If it shows =nil= or signals an error, then you don't.
55 Failing that, jabber.el will use the starttls.el library, which requires that the GnuTLS command line tool "gnutls-cli" is installed.
57 In Debian-based distributions, "gnutls-cli" is in the "gnutls-bin" package.
59 The above applies to STARTTLS connections, the most common way to encrypt a Jabber connection and the only one specified in the standards. STARTTLS connections start out unencrypted, but switch to encrypted after negotiation. jabber.el also supports connections that are encrypted from start. For this it uses the tls.el library, which requires either "gnutls-cli" or the OpenSSL command line tool "openssl" to be installed.
61 To use the latter form of encryption, customize =jabber-account-list=.
63 Note that only the connection from you to the server is encrypted; there is no guarantee of connections from your server to your contacts' server being encrypted.
69 To connect to a Jabber server, type =C-x C-j C-c= (or equivalently =M-x jabber-connect-all=) and enter your JID. With prefix argument, register a new account. You can set your JID permanently with =M-x jabber-customize=.
71 Your roster is displayed in a buffer called *-jabber-*. To disconnect, type =C-x C-j C-d= or =M-x jabber-disconnect=.
73 You may want to use the menu bar to execute Jabber commands. To enable the Jabber menu, type =M-x jabber-menu=.
75 For a less terse description, read the enclosed manual.
77 For bug reports, help requests and other feedback, use the trackers and forums at the project page mentioned above.
81 :CUSTOM_ID: configuration
83 All available configuration options are described in the manual. This section only serves to point out the most important ones.
85 To change how you are notified about incoming events, type =M-x customize-group RET jabber-alerts=.
87 To activate logging of all chats, set =jabber-history-enabled= to =t=. By default, history will be saved in =~/.jabber_global_message_log=; make sure that this file has appropriate permissions. Type =M-x customize-group RET jabber-history= for more options.
89 By default, jabber.el will send a confirmation when messages sent to you are delivered and displayed, and also send "contact is typing" notifications. To change this, type =M-x customize-group RET jabber-events=, and set the three =jabber-events-confirm-*= variables to nil.
91 By default, jabber.el logs all MUC presence announcements to the chat buffer. With the advent of mobile clients that frequently lose and regain network connectivity, the user left/joined messages can flood the chat. Customize =jabber-muc-decorate-presence-patterns= to hide or deemphasize presence announcements. See the manual for details [[info:jabber#Presence announcements][(info "(jabber) Presence announcements")]].
95 :CUSTOM_ID: file-transfer
97 This release of jabber.el contains support for file transfer. You may need to configure some variables to make it work; see the manual for details.
101 :CUSTOM_ID: xmpp-uris
103 It is possible to make various web browsers pass links starting with "xmpp:" to jabber.el. In the ideal case, this works right after running "make install". Otherwise, see the manual, section "XMPP URIs".
107 :CUSTOM_ID: further-reading
109 Documentation for developers is present in [[file:DEV.org][DEV.org]].
113 :CUSTOM_ID: how-to-guides
115 See also - [[file:DEV.org#how-to-guides][how-to guides in the developer documentation]].
117 ** How to install jabber.el
119 :CUSTOM_ID: installation
123 :CUSTOM_ID: from-melpa
125 1. Add the MELPA repositories to your Emacs - https://melpa.org/#/getting-started
126 2. Type =M-x package-install RET jabber RET=
128 If all goes well, =jabber.el= commands like =jabber-connect= should now be available in the =M-x= menu.
132 :CUSTOM_ID: from-source
134 1. Ensure you have =git=, and Emacs 27.1 or newer
136 2. Clone the repository by typing the following into a terminal -
138 mkdir ~/emacs-jabber/
140 git clone https://codeberg.org/emacs-jabber/emacs-jabber
144 3. Add the following lines to your =init.el= -
145 #+BEGIN_SRC emacs-lisp
146 (add-to-list 'load-path "~/emacs-jabber/lisp/")
147 (load "~/emacs-jabber/jabber-autoloads")
149 ...and, while still in your =init.el=, type =M-x eval-buffer RET=.
151 If all goes well, =jabber.el= commands like =jabber-connect= should now be available in the =M-x= menu.
153 To install the Info documentation, copy =jabber.info= to =/usr/local/info= and run ="install-info /usr/local/info/jabber.info"=.
155 * TODO maintenance [16%]
157 :CUSTOM_ID: maintenance
159 1. [ ] Satisfy =M-x checkdoc=
160 2. [ ] Use =rx= where regular expressions get hairy
161 * [ ] =jabber-jid-username=
162 * [ ] =jabber-jid-server=
163 * [ ] =jabber-jid-resource=
164 3. [X] Remove dependency on hexrgb.el (it's not available on MELPA)
165 4. [ ] Migrate tests to ERT/Buttercup/etc
166 5. [ ] Add Windows support to developer tutorial
167 6. [ ] Create testing for tutorial
175 :CUSTOM_ID: developers
179 + Kirill A. Korinskiy
186 :CUSTOM_ID: contributors
189 - network transport functions
190 + Anthony Chaumas-Pellet
194 - watch functionality
195 + Mario Domenech Goulart
200 - Chat State Notifications
204 - notifications.el support
206 - notifications.el support
207 - libnotify.el support
210 - network transport functions
214 + Valery V. Vorotyntsev
215 - GMail notifications
222 + Michael Cardell Widerkrantz
224 + Case Duckworth (acdw)
225 - [[https://codeberg.org/emacs-jabber/emacs-jabber/pulls/2][PR #2]]
226 + Hugh Daschbach (hdasch)
227 - MUC presence announcements
228 - Enable XEP-0280 (message carbons) by default
232 :CUSTOM_ID: maintainers
237 - HTTP Upload support
238 - documentation for FSM and its use in this project
240 - literate Org migration
241 - Makefile (shoutout to tomasino of #team@irc.tilde.chat for the Makefile-debugging help)
242 - migration back to traditional source files