12

I'm done with Vim for good.

Comments
  • 1
    I smell a real rant here. care to elaborate?
  • 0
    Here's a link to my related rant.

    https://devrant.io/rants/509526/...
  • 0
    @magicMirror configuration sucks big time. I wrote some vim scripts for automating parenthesis for writing clojure. It was going good. After some time i copied some codes into the configuration and nothing works now. The code seems ok. Vim script is can be confusing alot unlike Emacs lisp which is readable and straightforward.
  • 1
    I like vimeo
  • 1
    So you went back ? 😂
  • 2
    @Almost I'm actually starting to like vs code .. its a nice editor
  • 1
    My fallen brotheh, come back :(
  • 1
    One of my finals required me to use VI. Professor said he would know if we didn't. I was a bit rusty and got stuck in VIM and ended up deleting my entire final when I was about 50% done. I had to restart, but I did everything in sublime. He never found out.
  • 0
    @thesinding yes. The force is strong with Emacs.
  • 0
    @dontbeevil You haven't felt the power of the Force.
  • 0
    @tahnik I've been on the dark side too long. It's time I return to being Jedi Knight.
  • 1
    @jaaywags editors only matter for programmer. It's for our own sake to choose the editor we feel comfortable in.
  • 1
  • 1
    @CSaratakij it's good but Emacs is Emacs.
  • 2
    @CSaratakij personally I gave up on multimode editors. I use 'ne' as a cli editor for everyday use. Less painful, cool learning curve. Lacks some extensibility but since I am coding a runtime for a generic byte code (aimed for lisp but well) I may add a real scripting interface to it
  • 0
    @QCat you're doing lisp?? That's amazing man.
  • 1
    @theothergod I am not doing lisp, I am making lisp 😁 But Lisp is an easy language to parse and execute, with the only complicated point of variable arity of the procedures that is painful for a stack based VM
  • 0
    @QCat yeah LISP is ama-wait for it-zing.
Add Comment