To install this package, run in Emacs:
M-x package-install RET ement RET
Ement.el is a Matrix client for Emacs. It aims to be simple, fast, featureful, and reliable.
Feel free to join us in the chat room: https://img.shields.io/matrix/ement.el:matrix.org.svg?label=%23ement.el:matrix.org
Ement.el is published in GNU ELPA, so it may be installed in Emacs with the command
M-x package-install RET ement RET. This is the recommended way to install Ement.el, as it will install the current stable release.
Ement.el is also available in GNU Guix as
Ement.el is also available in Debian as elpa-ement.
master branch of the Git repository is intended to be usable at all times; only minor bugs are expected to be found in it before a new stable release is made. To install from this, it is recommended to use quelpa-use-package, like this:
;; Install and load `quelpa-use-package'. (package-install 'quelpa-use-package) (require 'quelpa-use-package) ;; Install Ement. (use-package ement :quelpa (ement :fetcher github :repo "alphapapa/ement.el"))
Ement.el is intended to be installed with Emacs's package system, which will ensure that the required autoloads are generated, etc. If you choose to install it manually, you're on your own.
ement-connectto connect. Multiple sessions are supported, so you may call the command again to connect to another account.
ement-list-roomsto view the list of joined rooms.
ement-view-roomto view a room's buffer, selected with completion.
ement-create-roomto create a new room.
ement-invite-userto invite a user to a room.
ement-join-roomto join a room.
ement-leave-roomto leave a room.
ement-forget-roomto forget a room.
ement-tag-roomto add (or with interactive prefix, remove) a tag on a room (including favorite/low-priority status).
ement-list-membersto list members in a room.
ement-send-direct-messageto send a direct message to a user (in an existing direct room, or creating a new one automatically).
ement-room-edit-messageto edit a message at point.
ement-room-send-fileto send a file.
ement-room-send-imageto send an image.
ement-room-set-topicto set a room's topic.
ement-room-occurto search in a room's known events.
ement-ignore-userto ignore a user (or with interactive prefix, un-ignore).
ement-room-set-message-formatto set a room's message format buffer-locally.
These bindings are common to all of the following buffer types:
M-RET(while writing in minibuffer:
C-c ')(Use command
ement-room-compose-orgto activate Org mode in the compose buffer.)
ement-room-send-message-filter(which enables Org format by default), or by calling
ement-room-compose-orgin a compose buffer (which enables it for a single message). Then Org-formatted messages are automatically converted and sent as HTML-formatted messages (with the Org syntax as the plain-text fallback). You can send syntax such as:
SPCrepeatedly, you can cycle through and read all rooms with unread buffers. (If a room doesn't have a buffer, it will not be included.)
C-x r m. This is especially useful with Burly: you can arrange an Emacs frame with several room buffers displayed at once, use
burly-bookmark-windowsto bookmark the layout, and then you can restore that layout and all of the room buffers by opening the bookmark, rather than having to manually arrange them every time you start Emacs or change the window configuration.
setqshould not be used for certain options, because it will not call the associated setter function. Users who have an aversion to the customization system may experience problems.
Emacs may not display certain symbols and emojis well by default. Based on this question and answer, you may find that the simplest way to fix this is to install an appropriate font, like Noto Emoji, and then use this Elisp code:
(setf use-default-font-for-symbols nil) (set-fontset-font t 'unicode "Noto Emoji" nil 'append)
Ement.el doesn't support encrypted rooms natively, but it can be used transparently with the E2EE-aware reverse proxy daemon Pantalaimon. After configuring it according to its documentation, call
ement-connect with the appropriate hostname and port, like:
(ement-connect :uri-prefix "http://localhost:8009")
Why write a new Emacs Matrix client when there is already matrix-client.el, by the same author, no less? A few reasons:
matrix-clientuses an older version of the Matrix spec, r0.3.0, with a few elements of r0.4.0 grafted in. Bringing it up to date with the current version of the spec, r0.6.1, would be more work than to begin with the current version. Ement.el targets r0.6.1 from the beginning.
matrix-clientdoes not use Matrix's lazy-loading feature (which was added to the specification later), so initial sync requests can take a long time for the server to process and can be large (sometimes tens of megabytes of JSON for the client to process!). Ement.el uses lazy-loading, which significantly improves performance.
matrix-clientautomatically makes buffers for every room a user has joined, even if the user doesn't currently want to watch a room. Ement.el opens room buffers on-demand, improving performance by not having to insert events into buffers for rooms the user isn't watching.
matrix-clientwas developed without the intention of publishing it to, e.g. MELPA or ELPA. It has several dependencies, and its code does not always install or compile cleanly due to macro-expansion issues (apparently depending on the user's Emacs config). Ement.el is designed to have minimal dependencies outside of Emacs (currently only one,
plz, which could be imported into the project), and every file is linted and compiles cleanly using makem.sh.
matrix-clientuses EIEIO, probably unnecessarily, since few, if any, of the benefits of EIEIO are realized in it. Ement.el uses structs instead.
matrix-clientuses bespoke code for inserting messages into buffers, which works pretty well, but has a few minor bugs which are difficult to track down. Ement.el uses Emacs's built-in (and perhaps little-known)
ewoclibrary, which makes it much simpler and more reliable to insert and update messages in buffers, and enables the development of advanced UI features more easily.
matrix-clientwas, to a certain extent, designed to imitate other messaging apps. The result is, at least when used with the
matrix-client-framecommand, fairly pleasing to use, but isn't especially "Emacsy." Ement.el is intended to better fit into Emacs's paradigms.
matrix-client's long name makes for long symbol names, which makes for tedious, verbose code.
ementis easy to type and makes for concise, readable code.
matrix-clientand hopes to write simpler, more readable, more maintainable code in Ement.el. It's hoped that this will enable others to contribute more easily.
Note that, while
matrix-client remains usable, and probably will for some time to come, Ement.el has now surpassed it in every way. The only reason to choose
matrix-client instead is if one is using an older version of Emacs that isn't supported by Ement.el.
window-scroll-functions, which sometimes caused a strange race condition that could cause Emacs to become unresponsive or crash.)
ement-taxy-room-listview no longer automatically refreshes the list if the region is active in the buffer. (This allows the user to operate on multiple rooms without the contents of the buffer changing before completing the process.)
ement-room-scroll-up-mark-readselects the correct room window.
ement-room-list-avatarsdefaults to what function
After almost two years of development, the first tagged release. Submitted to GNU ELPA.
Bug reports, feature requests, suggestions — oh my!
Ement.el is published in GNU ELPA and is considered part of GNU Emacs. Therefore, cumulative contributions of more than 15 lines of code require that the author assign copyright of such contributions to the FSF. Authors who are interested in doing so may contact email@example.com to request the appropriate form.
An Org-formatted version of the Matrix spec is available in the meta/spec branch.