Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Bwahahaha! I think no-one has posted a solution for the past 2 years because you are all EVIL emacs users!</p> <p>Truth be told, I'm trying out evil-mode at the moment myself and I just solved this problem on my system. Put this in your .emacs file and smoke it:</p> <pre><code>'(evil-default-cursor (quote (t "white"))) </code></pre> <p>I just opened <a href="https://bitbucket.org/lyro/evil/issue/342/evil-default-cursor-setting-should-default" rel="nofollow noreferrer">a bug</a> against the Evil repository in bitbucket.</p> <p>For myself, I found that after the 6 years or so it took to really become proficient at emacs, the multi-key chords were hard on my tendons. Evil-mode may allow me to use emacs again, which is a good thing. As <a href="https://stackoverflow.com/users/978588/benedict">Benedict</a> says (in the context of Functional Programming), "<a href="https://softwareengineering.stackexchange.com/questions/212515/why-is-tight-coupling-between-functions-and-data-bad/212537#212537">Some evil is often necessary to get work done.</a>" It seems that may apply to Emacs as well.</p> <p>P.S. For anyone feels this answer is just <a href="http://www.paulgraham.com/disagree.html" rel="nofollow noreferrer">DH0</a> or otherwise immature and inappropriate, the mostly tongue-in-cheek <a href="http://en.wikipedia.org/wiki/Editor_war" rel="nofollow noreferrer">feud</a> between Emacs and VI users has raged for years. Emacs has it's own <a href="http://www.emacswiki.org/emacs/ChurchOfEmacs" rel="nofollow noreferrer">Church of Emacs</a>, VI has the video game, <a href="http://wordwarvi.sourceforge.net/" rel="nofollow noreferrer">World War VI</a>. So it is no surprise that the most successful port of VI keybindings to Emacs was named evil-mode (evil has the word VI in it). I like both editors and laud the evil developers who finally made VI keybindings work inside emacs.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload