New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot load on windows #5284

Closed
chantisnake opened this Issue Feb 28, 2016 · 7 comments

Comments

Projects
None yet
3 participants
@chantisnake

chantisnake commented Feb 28, 2016

I have followed the instruction:

I have set the HOME dir:
capture

I have cloned space emacs both in $HOME and AppData\Roaming:
capture

I have used the recommended windows setting and I have used the stable release version:
capture1
(I also tried the mingw version...)
capture

the spacemacs is simply not loading when I started emacs... I don't know what to do...
There is no bug at all, it is just not loading...

@chantisnake

This comment has been minimized.

Show comment
Hide comment
@chantisnake

chantisnake Feb 28, 2016

I use the lower version and force load the init file, then everything works...

emacs -q -l "C:\Users\zcsxo\AppData\Roaming\.emacs.d\init.el"

god that feels good!

chantisnake commented Feb 28, 2016

I use the lower version and force load the init file, then everything works...

emacs -q -l "C:\Users\zcsxo\AppData\Roaming\.emacs.d\init.el"

god that feels good!

@chantisnake

This comment has been minimized.

Show comment
Hide comment
@chantisnake

chantisnake Feb 28, 2016

okay... another problem...

Symbol's function definition is void: projectile-mode

this is in latest version of spacemacs...

chantisnake commented Feb 28, 2016

okay... another problem...

Symbol's function definition is void: projectile-mode

this is in latest version of spacemacs...

@chantisnake

This comment has been minimized.

Show comment
Hide comment
@chantisnake

chantisnake Feb 28, 2016

emacs 24.5.1 works with 104, but not 105...

chantisnake commented Feb 28, 2016

emacs 24.5.1 works with 104, but not 105...

@TheBB

This comment has been minimized.

Show comment
Hide comment
@TheBB

TheBB Feb 28, 2016

Collaborator

Try starting with --insecure. Wipe your elpa directory first.

Collaborator

TheBB commented Feb 28, 2016

Try starting with --insecure. Wipe your elpa directory first.

@chantisnake

This comment has been minimized.

Show comment
Hide comment
@chantisnake

chantisnake Feb 28, 2016

That is actually another weird thing:
capture1
capture

chantisnake commented Feb 28, 2016

That is actually another weird thing:
capture1
capture

@StreakyCobra

This comment has been minimized.

Show comment
Hide comment
@StreakyCobra

StreakyCobra Feb 28, 2016

Contributor

be sure to remove your old .emacs file first, it's probably why .emacs.d/init.el of Spacemacs is not used. Also --insecure is a Spacemacs option, so be sure to use it when you start with the Spacemacs config. As @TheBB said, be sure to remove elpa first before starting again with --insecure

Contributor

StreakyCobra commented Feb 28, 2016

be sure to remove your old .emacs file first, it's probably why .emacs.d/init.el of Spacemacs is not used. Also --insecure is a Spacemacs option, so be sure to use it when you start with the Spacemacs config. As @TheBB said, be sure to remove elpa first before starting again with --insecure

@chantisnake

This comment has been minimized.

Show comment
Hide comment
@chantisnake

chantisnake Feb 28, 2016

That is why!... thanks, sorry for wasting your time...

chantisnake commented Feb 28, 2016

That is why!... thanks, sorry for wasting your time...

@syl20bnr syl20bnr changed the title from cannot load on windows to cannot load on windows Feb 28, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment