-
Notifications
You must be signed in to change notification settings - Fork 32
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
Spacemacs (emacs/vim) setup #22
Comments
@mjsteinbaugh here is my emacs set up, let me know if this doesn't work out. You can just use my You can stay up to date by running a git pull in your |
Amazing, thanks @roryk |
should we turn this into a markdown and make a pull request? |
@mistrm82 +1 for a markdown. Also, I noticed that the emacs version on O2 is too old for spacemacs, so it's be cool if HMS RC could update the version installed. Otherwise conda works. |
I don't actually use Emacs on O2; I just use |
Sweet I will check that out |
https://github.com/roryk/dotfiles/blob/master/spacemacs is my current configuration. It is basically stock spacemacs, with vim/evil mode turned on.
Hilighted changes from stock:
https://github.com/roryk/dotfiles/blob/28c508eb7431d4a8b3b6bed3cf553eb83ac8bb32/spacemacs#L60 this allows you to open up a remote terminal and then open files from it as if you were opening on that remote machine, but on your local emacs session.
R/ESS specific stuff:
https://github.com/roryk/dotfiles/blob/28c508eb7431d4a8b3b6bed3cf553eb83ac8bb32/spacemacs#L368 this line makes it so ESS stops indenting single # comments.
In your .emacs.d/private/polymode directory, add this to be able to edit RMarkdown documents and have proper syntax hlighting in code blocks:
The text was updated successfully, but these errors were encountered: