This has a benefit of not assuming that the user .emacs.d/ is in the
user home directory. Should continue to work as expected when this is
the case, but you could also start a fresh Emacs session like
so (assumes OSX):
open -a Emacs.app -n --args -q -l /path/to/emacs.d/init.el
So you don't have to muddle with symlinking your ~/.emacs.d or replacing
it with another just to try Spacemacs (or any other config). Note, that
this won't work with `after-init-hook` which doesn't appear to run when
Emacs is run with -q flag. As a result the `dotspacemacs/config` in your
.spacemacs won't run.
I cherry-picked it and played with it.
There is a major problem with this approach: all `after-init-hooks` will
be triggered right away because the hook is run before the end of the
alternate init
file ([source](https://groups.google.com/forum/#!topic/gnu.emacs.help/IrMz48PQykk))
. It leads to numerous errors, I fixed the spacemacs ones but obviously
I cannot fix the errors from packages. The remaining errors don't
prevent spacemacs from working but they give a very bad impression on
spacemacs quality with errors logs in `*Messages*`.
For those reasons I revert back this change as well as the documentation
I added.
https://github.com/syl20bnr/spacemacs/pull/520
user-emacs-directory is defined by emacs when load config, in most case
it's value is ~/.emacs.d. We setup this variable in init.el to make
existing emacs user can test spacemacs by
emacs -q -l ~/spacemacs/init.el
without change their own ~/.emacs.d config.
Signed-off-by: Yen-Chin Lee <coldnew.tw@gmail.com>
Load paths are now registered in `core/load-paths.el`
Libraries are in `core/lib`
Move `ht.el` to `lib`
Add `mocker.el` to `lib`
Tests are in test,
- unit tests files suffix is `utest.el`
- functional tests files suffix is `ftest.el`
