Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>What I like to do is split my terminal once horizontally, and then split the bottom pane once vertically. </p> <p>In the top pane I have <code>vim</code> (<code>emacs</code> works too if you're an <code>emacs</code> person) with the NERDTree plugin (acts like the project folder/file browser in text editors). On the bottom left I have SBT continuous compilation (<code>sbt ~compile</code>). I use the bottom right pane to actually run code (tests, etc.).</p> <p>Regarding auto-completion, you can try something like the Snipmate plugin for <code>vim</code>.</p> <p>Also, as stated by Ivan, if you end up using <code>emacs</code> ENSIME seems to be widely liked - unfortunately there doesn't seem to be an ENSIME port for <code>vim</code> yet, at least to my knowledge.</p> <p>With this setup, I edit in the top pane, and once I save a file, I get near immediate feedback by just glancing on the bottom left and know when I typo'ed something, or maybe my code is just plain wrong, stuff like that.</p> <p>On a slightly related note, I used to use IDE's but they got too messy for my taste (back then I was writing C and C++) so I moved to just a text editor (e.g. Chocolat, Sublime Text 2) and used a terminal, and that was fine for me for about a year. Then this summer I really sat down and tried going <code>vim</code> only and I can honestly say I'm much more productive in my all terminal setup than what I was before. Just my 2 cents.</p> <p>This all also has the added benefit of working on remote servers as well.</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