Skip to content

spp/.emacs.d

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

66 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

WHAT?
-----
This is my .emacs.d folder. I've tried to keep it consistent across machines running Debian Squeeze and Snow Leopard. 

WHY?
----
How is this different from emacs-starter-kit you ask? I tried customizing the emacs-starter-kit but I couldn't satisfactorily make that happen. Most of my frustrations revolved around ELPA. It is brittle and the archives don't contain a whole lot of packages. Many of these packages aren't being actively maintained any more. Good folks have created their own forks and updated them with lots more features. If I were to use a standard archive, I would still have to refer to these non-standard locations in order to get the packages I want. Also, I wanted to churn out some Elisp code and get a better understanding of how extensible Emacs really is.

HOW?
----
To start using this, do the following:

cd ~						# Go to your home folder	    
rm .emacs					# Remove the .emacs file if it exists
git clone https://github.com/habib/.emacs.d.git # Clone this repository
cd .emacs.d					
git submodule init				# Update the dependencies
git submodule update 				# Wait patiently if you hail from a bandwidth starved nation
cd packages/rinari				# Goto the rinari mode folder
git submodule init
git submodule update				# Rinari mode has its own dependencies

The .gitmodules file will tell you that most of the packages are from https://github.com/emacsmirror/ . That's an awesome resource and I thank the maintainers. 

The themes are stored in the 'themes' folder. I prefer a slightly modified zenburn thats packaged with this. If you prefer another theme, put it in the themes folder and modify the init.el file accordingly. All the packages are stored in the 'packages' folder. The list keeps changing. See .gitmodules for an up-to-date listing.

WHAT ELSE?
----------
You'll need to install ack (or ack-grep in Debian), exuberant-ctags and cscope for all the packages to work. 

If you write Ruby code, you will love RSense mode. Extract the contents of the latest stable version (0.3 as of now) to your ~/opt folder. Follow this for more information: http://cx4a.org/software/rsense/

WHAT NEXT?
----------
* Emacs-IDE is a neat idea. However it doesn't play well with IDO mode. The alternative is CEDET which is moody and clunky. Either fix Emacs-IDE or get rid of it.

* Steal ruby-mode settings from the emacs-starter-kit. <- PARTIALLY DONE.

* Store machine-specific settings separately.

* Make rspec-mode and shoulda-mode work properly.

* Wire up AutoComplete and Yasnippet. 

* Set up JavaScript lint checking with a Node.js server. Overkill? Yes. Absolutely awesome? You betcha!

* Work towards a solution for cleanly maintaining packages. The workflow can be as follows:
The user points to a git repo which will added as a submodule, fetched and compiled. The compiled .elcs are stored out of git's purview. The user can also get packages via ELPA if so desired. el-get does most of what I want and I am looking forward to using it.

About

My .emacs.d folder

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published