14

Just out of curiosity, I wanted to try emacs + evil. Here's what I've done so far:

  • Installed emacs 24 on Windows 7 -- went well

  • Created an .emacs file in C:\Users\name\AppData\Roaming\ (where .emacs.d ended up)

  • Added the following to that .emacs file

    (setq package-archives '(("ELPA" . "http://tromey.com/elpa/")
                             ("gnu" . "http://elpa.gnu.org/packages/")
                             ("marmalade" . "http://marmalade-repo.org/packages/")))

  • started emacs then M-x package-list-packages

  • selected evil, evil-leader, evil-numbers with i then x to install

  • restarted emacs

Evil shows as installed in package-list-packages and the evil files are present in .emacs.d\elpa, but evil doesn't seem to be loaded when I start emacs (No <N> in the status bar).

JUST starting with emacs. Not managing to get much out of it except for a lot of beeps. Want to start simple and use it for a few days before possibly moving forward with further extensions.

Shay
  • 1,368
  • 11
  • 17

1 Answers1

29

You should add following s-expressions to your .emacs.

(package-initialize)
(evil-mode 1)        ;; enable evil-mode
N.N.
  • 8,336
  • 12
  • 54
  • 94
syohex
  • 2,293
  • 17
  • 16
  • 1
    Thank you. Worked perfectly. Afraid I had to drop emacs after just one night. Nothing against emacs, there's just too much outdated information on the net to filter through. After trying a half-dozen (worked for someone once-upon-a-time) "solutions" to a few problems, I gave up. The best thing about vim is that I already know how to use it. – Shay Dec 08 '12 at 03:36
  • @Shay As for getting used to Emacs, I would try to stick with the menu bar until you get used to the keyboard shortcuts. The menu bar always displays a keybinding if one exists, so you'll learn them by osmosis, so to speak. There is a steep getting-it-functional learning curve involved with Emacs, but once you get over that -- it's a breeze. – Sean Allred Feb 08 '13 at 21:12
  • 4
    Emacs has an abundance of fully up-to-date documentation contained within it. You don't need to resort to "outdated information on the net". Not to discount the learning curve -- it's still lengthy -- but absence of good relevant documentation is really *not* a problem that Emacs suffers from. – phils Sep 13 '13 at 09:47
  • +1 @phils I believe that Emacs documentation could have guided us. Could you give me some pointers or where/how to look for such issues? As beginners we would love to hear from you. – vijiboy Mar 23 '16 at 05:52
  • 1
    vijiboy: (1) In general... the in-built tutorial (`C-h t`) is very valuable for newcomers, and the well-indexed Info manuals (`C-h i`) are always a sensible place to look. Take good note of the notes at the top of the Info directory. Once you know how to use the Info reader (including the indexes and full-text isearch), you'll have taken some solid steps towards learning how to learn Emacs. – phils Mar 23 '16 at 06:54
  • 1
    (2) For some specific library such as Evil, I would typically either use `M-x find-library` to read the Commentary in the code comments towards the top of the file (a standard place for documentation to live), or see if the package installed its own Info manual (I see that it does). – phils Mar 23 '16 at 06:57
  • To keep it clean @phils, I could make it a seperate question and mark your answer. let me know ... – vijiboy Mar 31 '16 at 10:45
  • Hello @lanza. I don't understand your comment. What it is that doesn't work for you? – phils Aug 02 '18 at 08:24