gister is a command line tool for managing GitHub gists.
After publishing files to gist.github.com, this tool will:
- automatically clone the gist repository to local
- index the content of your gist for code search
- fetch meta info (e.g. description, url) of the gist from GitHub and add them to
You can also use
gister to sync your gists (created and starred)
between gist.github.com and your machine.
For Linux, BSD, etc, you also need
For Cygwin, you need putclip/getclip provided by cygutils-extra.
(Mas OS X users should be fine with the preinstalled pbcopy/pbpaste.)
Mac OS X users also need GNU versions of
xsel users should use
gist.rb v4.1.2+, since there is a bug bitting xsel users in previous versions.
To search gists on your local machine. If not available, fallbacks to
If available, invokes
legit syncto sync gist repository. Legit will stash, fetch, rebase/merge, push, and unstash if necessary.
developbranch of legit allows configuration for merge policy:
* The default smart merge (rebase when suitable) * Always merge, never rebase (since [21bb7ed]) * Always rebase, never merge (since [252b1eb]) * Fast forward merge only (since )
If legit is not available, invokes
git pull & git pushfor clean gist repositories, and reports
DIRTY $gist_idfor dirty gist repositories.
; basher install weakish/gister
Requires basher version:
; basher uninstall weakish/gister
git clone https://github.com/weakish/gister.git cd gister make install
config.mkif you do not want to install it to
- Compatible with both GNU and BSD make.
; cd gister ; make uninstall
For the first time, you need to run
gister init to associate your GitHub account and configure the directory to store local copies of your gists.
After that, you may run
gister sync to fetch all your gists (created and starred) to local.
sync can only fetch up to 10 million gists for you. If you have more than 10 million gists, you need to modify the source of
gister to lift the limit.
Whenever you want to publish a gist, just use
gister description file.txt ...
This will create the gist with the provided description, clone the gist repo, and put the gistid to clipborad.
Note: you must provide gist description, otherwise
gister will fail.
gister will pass all arguments to gist as
gist -c -o -d description ..., so you can use other options that gist understands, e.g.
gister description -P will work.
If you've edited your gists at
gist.github.com or local machine, without pull/push changesets, you can sync all your gists via
If you've deleted your gists at
gister sync, the directories of deleted gists at your local machine will be marked with a prefix
Search all of your gists:
gister search regexp
codesearch is installed,
regexp is RE2 (nearly PCRE).
Otherwise it is ERE, a.k.a
Export a gist (available at local) to a git repository, with its full history:
; cd git-repo-root ; gister export gist_id sub_directory_name branch_name
The content of the gist will be exported to
and the merging message will uses
From version 1.0.0,
gister uses a different storage structure.
If you have used
gister <1.0.0, then you need to run this command to migrate:
/path/to/your/gists |-- gists.list # a list of all your gists (including meta info) |-- repo # git repositories of your gists |-- tree # working directory of your gist repositories |-- 123456 # an example of gist |-- _123567890 # an example of gist which you have deleted on gist.github.com |-- ... `-- .csearchindex # code search index (optional)
Send pull requests or issues at: