To get started clone the repository of the
Currently this is the only available collective and, for the time
being this manual assume that you use that.
This collective already assimilated a few drones in addition to
diff-hl, and their dependencies. These drones are not required by
borg but their use is highly recommended.
Instructions on how to bootstrap a configuration without basing it on
emacs.g collective will be added in the near future.
emacs.g repository to either
~/.emacs.d, or for testing
purposes to any other location. This repository contains a
lib/borg/borg.mk and defines an additional target whose
purpose is to make that file and
lib/borg/borg.sh available. Run
bootstrap-borg to clone the
borg repository. That does not completely
borg repository but it makes the latest version of the
mentioned files available. Now that these files are available you can
make bootstrap to get and configure all submodules (including the
borg submodule) and to build all drones.
git clone email@example.com:emacscollective/emacs.g.git ~/.emacs.d cd ~/.emacs.d make bootstrap-borg make bootstrap
If you cloned to somewhere else than
~/.emacs.d, then you can use that
emacs -Q --load /path/to/emacs.g/init.elc.
For drones whose upstreams are on Github or Gitlab the
collective uses the
ssh protocol by default, which is a problem if you
don’t have accounts there and have not properly setup your keys.
Luckily this can easily be fixed using the following right after
cloning the super-repository.
git config --global url.https://github.com/.insteadOf firstname.lastname@example.org: git config --global url.https://gitlab.com/.insteadOf email@example.com:
During package compilation you may notice the submodules relating to
those packages become dirty due to the compilation outputs not being
ignored in those submodules. For this reason it is useful to ignore
these outputs globally, for example in your
*.elc *-autoloads.el dir
You may discover more things that you’ll want to ignore this way as you