|Ryan Rix 5bf61e088f Make these stay as float||2 years ago|
|test||3 years ago|
|.gitignore||3 years ago|
|.travis.yml||3 years ago|
|Cask||3 years ago|
|LICENSE||3 years ago|
|Makefile||3 years ago|
|README.org||3 years ago|
|matrix-api.el||2 years ago|
|matrix-client-handlers.el||2 years ago|
|matrix-client-modes.el||3 years ago|
|matrix-client.el||2 years ago|
|matrix-helpers.el||3 years ago|
|matrix-sauron.el||3 years ago|
|scratch.el||3 years ago|
matrix-client is installable via MELPA. Otherwise you can add this directory to your
and =(require 'matrix-client).
There are two parts, a low-level API, and a terrible barely-alpha-quality client.
Either deploy your own homeserver or register account on the public homeserver
https://matrix.org/beta/#/login . After you've done that,
M-x matrix-client will set you up with
buffers corresponding to your Matrix rooms. You can join new ones with /join, leave with /leave or
/part, and hook in to the custom functions provided by
matrix-api is a low-level API right now; I'm planning to wrap it with high-level API that lets you easily
per-room events, and that sort of thing, and eventually a full-fledged Matrix client. The API itself
is pretty tightly based on the official Python API.
(let ((matrix-homeserver-base-url "https://yourhs.org")) (unless matrix-token (matrix-login-with-password "@you:yourhs.org" "[REDACTED]")) (matrix-initial-sync 1) (matrix-send-message "!yourroom:matrix.org" "Test post please ignore"))
git format-patchstyle patch
git format-patch --to email@example.com master..HEAD > YOURBRANCHNAME.patch
Project Discussion happens in
See LICENSE in the root of the repository for legal information.