|vaeringjar 9c6db29d57 Move custom set faces and vars to their own el.||1 month ago|
|examples||1 month ago|
|src||1 month ago|
|.gitignore||2 years ago|
|README.org||1 month ago|
Originally intended to turn emacs into an IDE, but now just my personal set of el files to replace my .emacs config.
Clone protoculture into your .emacs.d and then add this to your .emacs file.
(add-to-list 'load-path (expand-file-name "~/.emacs.d/protoculture/src")) (require 'protoculture)
To customize features or add to an existing init.el or .emacs file, it might look like the following with your own custom theme and face vars:
(add-to-list 'load-path (expand-file-name "~/.emacs.d/protoculture/src")) (require 'protoculture-packages) (require 'protoculture-dired) (require 'protoculture-backup-directory-alist) (require 'protoculture-comment) (require 'protoculture-indentation) (require 'protoculture-autocomplete) (require 'protoculture-snippet)
Copyright 2017 vaeringjar Code distributed under the AGPLv3+.
For now, some of this resides in uncommited sandbox.el.
Due to the omnipotent role of full stack, this might not include everything.
These help with any init and have little or no configuration.
The emacs-goodies-el meta package from apt no longer seems to work, so one should avoid using it. If already installed, remove it and then reinstall all emacs packages within the editor.
Gnus with some versions of Emacs seems to have an issue loading the .gnus file relative to ~/ when the Emacs init file does not reside in ~/. However, .authinfo and .newsrc seem to load just fine. As a workaround, use `make prime f=build/whichever.el` to place a .emacs file in ~/.