A docker image featuring super-emacs
1.0K

An out-of-the-box Emacs configuration with super-powers
super-emacs can be used in two ways.
Getting it from GitHub is easier of the two methods. You just need to clone the repository on your local workspace like:
git clone https://github.com/myTerminal/super-emacs.git
Then the only next step would be to make sure that .emacs.d is at the root of your home directory.
You can either place it there manually or otherwise create a soft-link from its location to the home directory.
ln -s </path/to/cloned/project>/super-emacs/.emacs.d ~/.emacs.d
A clear advantage of the above method would be that you can pull updates from upstream with almost no effort.
Once done, start Emacs to enjoy new super-powers.
Emacs 27 comes with XDG support and hence will also work with ~/.config/emacs. To be able to use super-emacs that way (which may as well be the only way soon), you can link it in the following way:
ln -s </path/to/cloned/project>/super-emacs/.emacs.d ~/.config/emacs
super-emacs is also available on Docker. To start it, run a command that looks like:
docker pull myterminal/super-emacs
C-x is pressed, using which-key<f5>Refer config-key-bindings.el for all the pre-configured key-bindings for your convenience.
The presence of this package is detected for use with ispell for spell-check. Refer to the official site for instructions on how to install it on your operating system.
It could be as easy as
# For Debian/Ubuntu
apt install aspell
OR
# For Fedora
dnf install aspell
OR
# For Arch Linux
pacman -S aspell
OR
# For macOS
brew install aspell
depending upon your operating system.
To be able to work with R Markdown files, super-emacs comes pre-configured with all the required packages except for an external dependency on R which needs to be installed on the system.
Not everyone has the same setup and that means that you can (and may) change the configuration files according to your need. However, if you plan to clone this project, use it for your Emacs through a soft-link and pull updates from upstream regularly, there's a high probability that future improvements may end up resulting in merge conflicts on your local workspace. To solve this problem (and according to a suggestion from @ericllazarus), super-emacs has been redesigned in a way that it now enables the user to extend their configuration without causing conflicts with future updates. One recommended way of extending super-emacs is described below.
All configuration files under .emacs.d/super-emacs/basic and .emacs.d/super-emacs/standard can be extended through contents in their neigboring *-custom.el file. For example, if you plan to extend the file basic/packages.el, you can place your personal configuration in the file basic/packages-custom.el. super-emacs will load the files in the right order so that your custom configurations will override the ones from super-emacs. This way, whenever there's an update to the original file, there will be no merge conflicts and life would be so much simpler!
If you're looking for a light-weight setup, try ample-emacs.
For an even more comprehensive setup, refer to my personal configs.
Content type
Image
Digest
Size
443.9 MB
Last updated
about 5 years ago
docker pull myterminal/super-emacs