Live data from Hacker News

Neovim

github.com

191–200 of 372 posts

Re: Neovim

#191

Earlier quoted context omitted.

If you are comparing Word and Markdown to LaTeX I think it's clear you haven't really used LaTeX.

Oh get over yourself. Every one of the criticisms he levelled against latex is spot on, and you pick up on the fact that he mentions Word is easier to use (which, by a long, long way, it it).

> Word is easier to use (which, by a long, long way, it it).

Definitely initially for simpler.

But what about using it collaboratively, merging changes and comparing between versions? Especially large documents with a multitude of authors combined later (think journals).

What about documents with programmatically generated content?

What about consistent formatting for your documents?

What about when Word gets confused by some element in the xml not visible to you?

Sure Word may be easier but there are limitations to it's use.

Re: Neovim

#192
post #176
post #124

Earlier quoted context omitted.

I have only superficially browsed vim sources some months ago. Vim source code is literally disgusting. The number of platforms vim runs on is close to Avogadro's number. It supports 5 or sth languages for customisation. I always had in my mind to fork the thing and remove all those languages, and strip off the compatibility stuff so it will be a pure Unix program, but I never got to do it. Also, the source repositor…

The stripped down version is called 'vi' :)

Well, I decided I'll play with acme* editor a little bit, if I can't get on well with it, I'll probably go that way.

* http://research.swtch.com/acme

Re: Neovim

#193
post #109

Earlier quoted context omitted.

> not too mention that vim became hip only in the last couple of years. Wait, what? Vim has been in use for a lot longer than that (it was released in 1991), and vi even longer (1976).

"Hip" does not mean remotely the same thing as "in use".

[deleted]

Re: Neovim

#194
Finally, someone took this step. I really appreciate his work.

Don't get me wrong. Vim is an awesome editor and it is the only editor I'm using now. I've been using it for decades and still cannot find an editor which can replace it. Sorry, emacs, I tried several times but failed. I know it's my problem but I'm too familiar with vim's short-cuts.

However, I do think we can still do some improvement on vim, especially on its plugin systems. If you wrote plugins for vim, you know what I'm talking about. For example, can you quickly tell me the differences between map nnoremap nnoremap? How to write comment in vimscript?

To me, vimscript seems like a language patched by lots of authors with inconsistent goals. It's not as cohesive as Emacs Lisp. And there are lots of historical reasons why they do that --- I know, it's backward compatibility. But you have to move forward at some time.

With that being said, I do think it is necessary to have an editor which keeps the good parts in vim and improve it by not considering too much about backward compatibility. I'm so glad that someone did it for us.

Re: Neovim

#195

Earlier quoted context omitted.

> 2014 > not zsh

I used to use zsh (including a giant, customized zshlovers .zhsrc) but I switched back to bash when I started administrating a few different servers. There's just something to be said for feeling totally comfortable and productive with a default environment. I'm also quite comfortable using plain old vi -- something a lot of other vim users can't stand.

Bash has also come a long way recently. I suspect a lot of the excitement over zsh comes from mac users who are stuck with what is now an ancient version of bash.

Re: Neovim

#196
post #40

Earlier quoted context omitted.

> ...should be ashamed people are still using Vim to write LaTeX in Bash running on terminal emulators. First, why? It works just fine. Second, is there anything better? I don't know of anything I would prefer to use. So until someone comes up with something, I'll stick to using Vim to write LaTeX in a Bash shell (might upgrade to zsh, we'll see).

For one example, just off the top of my head, most any remotely technically-inclined young person in 2014 knows that you use Ctrl-Z/X/C/V/A to undo, cut, copy, paste, and select all. (Or substitute Command if you're on a Mac--same basic idea.) They've got that down cold, along with a host of other ubiquitous editing conventions--Ctrl-Left/Right to jump words, Shift-arrowkeys to highlight, Home/End to jump to the begi…

Add this to ~/.vimrc

    " Make it behave more like a (Windows) GUI editor
    source $VIMRUNTIME/mswin.vim
    behave mswin
and use gvim - the GUI counterpart.

Re: Neovim

#197
This reminds me of the now dead https://github.com/chrizel/Yzis

Even though it has been tried a few times before and never seems to catch on I really like the idea and would be down to help except I haven't coded C in 15 years and don't really have any desire to go back. I wonder if there are parts I could help with in newer languages. It's always fun to pick up a project to learn a new language.

Re: Neovim

#198

Earlier quoted context omitted.

If you are comparing Word and Markdown to LaTeX I think it's clear you haven't really used LaTeX.

Oh get over yourself. Every one of the criticisms he levelled against latex is spot on, and you pick up on the fact that he mentions Word is easier to use (which, by a long, long way, it it).

It's an apples to oranges comparison.

I want to draw a conformal mapping diagram in word and also write a 3-vector of the navier-stokes equations.

Also, I want to do a lot of tensor arithmetic with tons of superscripts and subscripts and arrows.

Tell me how any of this is accomplished in Word please. Saying Word is easier to us is like saying BASIC is easier than C++.

Re: Neovim

#199
post #40

Earlier quoted context omitted.

> ...should be ashamed people are still using Vim to write LaTeX in Bash running on terminal emulators. First, why? It works just fine. Second, is there anything better? I don't know of anything I would prefer to use. So until someone comes up with something, I'll stick to using Vim to write LaTeX in a Bash shell (might upgrade to zsh, we'll see).

For one example, just off the top of my head, most any remotely technically-inclined young person in 2014 knows that you use Ctrl-Z/X/C/V/A to undo, cut, copy, paste, and select all. (Or substitute Command if you're on a Mac--same basic idea.) They've got that down cold, along with a host of other ubiquitous editing conventions--Ctrl-Left/Right to jump words, Shift-arrowkeys to highlight, Home/End to jump to the begi…

That seems like a bit of a straw man: the official OS X native version of vim, MacVim has literally all of those key map pings by default – cmd+c to copy, cmd+a to select all, etc.

Re: Neovim

#200
The more I think about this, the more I like it. I badly want my vim to be multi-threaded and a separate engine, especially one that had a queue based pub/sub type interface could really open up some cool possibilities. At that point if you could give it the ability to use operational transform for the changes it would make remote editing, as well as remote pairing work really well. I know floobits is doing something similar but I would have to think this would make that much easier to pull off.
Post reply on HN