senny/e-max — pull request #107 by jone (2012-01-21 16:16:13+00:00)
Title: Update install script.

I've worked on the install.sh and the .emacs.d templates, as discussed in #59.

## .emacs.d template:

- Moved bundle-list from `~/.emacs.d/init.el` to `~/.emacs.d/bundles.el`
- `~/.emacs.d/init.el` now only defines the e-max-path and loads e-max. It is not meant to contain any other things.
- A user-specific config file as well as a machine specific is created.
- A `~/.emacs.d/local.el` is created.
- A `~/.emacs.d/custom.el` is created.
- A `~/.emacs.d/bin/update-e-max` is created, symlinked to update.sh.

## install improvements:

- More verbose output. The user should see what is happening.
- Before doing anything, the changed paths are listed and the user can confirm.
- At the end there is a short summary with paths to configuration files and urls.

## e-max-theme
I've removed the `e-max-theme` variable (was in init.el). This was redundant, since the theme roller defines a `theme-roller-default-theme` custom - I've defined the default in custom.el. For me it was confusing - e-max-theme didn't really do anything.. @senny what do you think about this one?

## Updating

We need to be able to update .emacs.d with the update script somehow. But I'm not sure about what exactly should be done and what we will need in the future.

I'm also not sure about if and how we update the current user - should ensure somehow that they do have e.g. a bundles.el?

@senny please review. Webinstall is not easily possible to test on a non-master branch, so I'd just run it from a local clone..