Skip to content

xuchunyang/gitter.el

master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 

gitter.el

https://melpa.org/packages/gitter-badge.svg https://badges.gitter.im/M-x-Gitter/Lobby.svg

A Gitter client for GNU Emacs.

Prerequisites

  • cURL
  • Emacs 24.1 or newer

Install

Melpa

gitter.el is available from Melpa. After setting up Melpa as a repository and update the local package list, you can install gitter.el and its dependencies using M-x package-install gitter.

Manually

Add gitter.el to your load-path and require. Something like:

(add-to-list 'load-path "path/to/gitter.el/")
(require 'gitter)

If you want to avoid loading gitter.el at Emacs startup, autoload the gitter command instead of requiring.

Setup

Follow these steps to get your gitter token:

  1. Visit URL https://developer.gitter.im
  2. Click Sign in (top right)
  3. You will see your personal access token at URL https://developer.gitter.im/apps

Then put this line in your ~/.authinfo or ~/.authinfo.gpg (Don’t forget to replace here-is-your-token to yours):

machine gitter.im password here-is-your-token

Usage

Type M-x gitter to join a room and start chatting.

Limitation

If you are a serious Gitter user (I am not) and you compare this little program with other official Gitter clients, I guess you will probably be very disappointed: lack of functions and features, buggy etc, so now you have been warned. However, feedback, suggestion and patch are always welcome.

By the way, Gitter provides IRC access and there are several well-known IRC clients for Emacs.

To do

  • [ ] Markup message
    • plain link
    • Markdown link
    • Github-flavored Markdown image
    • @mention
    • Github #issue
    • Markdown inline code block (add syntax highlighting if it is possible and very easy)
    • Github-flavored fenced code block (add syntax highlighting if it has proper language tag)
    • Github-flavored indented with four spaces code block (prefer no syntax highlighting to avoiding guessing what language the code is in, I don’t like guess)
    • etc