Vim is already awesome as it is.
Neovim
341–350 of 372 posts
Re: Neovim
#342This 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.
The big difference here is that it's based on refactoring the existing codebase. While not the most glamorous job in the world, it's more realistic than attempting to recreate the product of 22 years of development starting from scratch.
Re: Neovim
#343Earlier quoted context omitted.
You're completely missing the GP's point. Whether or not LaTeX is better than MS Word for task X is besides the point. It's that LaTeX has many obvious opportunities for improvement, ways to drag it into the current age, while keeping all its fundamental strengths. As do many similarly old tools such as Bash, terminal emulators and Vim. These improvements aren't all that difficult to imagine, but they don't happen, b…
Why expend manpower and energy improving a working solution just to do so when you have so many other broken things that need fixing first? That's a fairly self-answering question. There's a reason the expression is "If it's not broken, don't fix it".
If you fear breaking it, why not replace / revolutionize instead. See GCC vs LLVM, X vs Wayland, C++ vs Go.
Re: Neovim
#344Earlier quoted context omitted.
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.
MacVim is not official and it doesn't ship with any version of OS X. It's nice that third parties have developed tools to try and bridge the gap, but it doesn't really address my original concern. Now, the OS X Terminal (and programs run through it, including vim) does support Cmd-C (after highlighting with the mouse), Cmd-V, and Cmd-A, because the OS can treat them as raw text without the terminal knowing anything a…
I really don't understand why neutral statements of fact get voted down. Is somebody way too emotionally invested in the discussion? Somebody reflexively downvotes anyone who makes them examine their assumptions? That dude I told off last week stalking me? Misclick? It's just weird.
Re: Neovim
#345It sounds like they have no interest in getting this stuff pushed back upstream? There's no mention of it on the home page. At this point it smells kind of Emacs/XEmacsish. Hope they can rally immense development effort.
The author of NeoVim (Thiago de Arruda) tried to add support for multi-threaded plugins to Vim and has been stymied[1]. I'm not sure how to get a patch merged into Vim. Bram Moolenar is the only person with commit access, and he's not a fan of most changes beyond bug fixes. My co-founder and I tried to add setTimeout & setInterval to vimscript[2]. Even six weeks of full-time effort and bending over backwards wasn't e…
Vim was created on Amiga, so that's explainable
Re: Neovim
#346Earlier quoted context omitted.
I agree with almost everything--except for backwards compatibility when it comes to throwing stuff out. There is definite value in it, especially when we're talking about something as old and widely used as vim! This is the part where people are surprised, but I am an extremist. I definitely think backwards compatibility should be among the lowest priorities when making decisions on improving software, especially and…
Large scale proof why this is a bad idea: Python 2.x vs Python 3 Those of you who don't know about this mess, it shouldn't be hard to find some rants by googling. Basically Python 3 broke backwards compatibility with python 2 without providing any compatibility layer at all, they just expected every third party library to switch "sooner or later". It's now 10 years down the road and nothing has really happened. Every…
Actually I see Python as a good example why you want to change. Python 3 has much cleaner concepts than Python 2: Strings are not byte arrays, use efficient generators by default, etc. On the other extreme take a look at C++: Lot's of ugly as hell syntax and pitfalls because of decades of backwards compatibility. See https://stackoverflow.com/questions/6939986/c-nested-constru... for an example of both.
> Everybody who gets shit done is still using 2.x because they need the old libraries.
And, btw., I hold each and everyone of these responsible as part of the chicken-and-egg problem.
Re: Neovim
#347I would love to have Bram Moolenaar's input on this project.
I've just sent an email to the vim_dev@googlegroups.com mailing list. I asked his opinion on the Neovim project.
The subject for my email is "Neovim", so let's wait and see what his opinion is.
Re: Neovim
#348Earlier quoted context omitted.
Writing my thesis with markdown was one of the best decisions i made. I wrote 99% of my master thesis in markdown (50 pages w/o interviews). 1) I didn't have a lot of images so i just wrote FIXME: Image Foo.png where they belonged. 2) I wrote my Citations Plain in there (e.g. Wocken, 1985, 7 ff.), using a special folder for all sources i really used in Mendeley. 3) Writing in markdown i could just c&p perfectly forma…
How do you get pagination with markdown? I would like to switch to markdown instead of using latex, because my needs are simple. But how can I convert markdown into something with support for pagination?
i actually converted it to rtf and imported it then in MS Word (On OS X). I took care of pagination there.
Actually the Plan was to typeset it in Indesign, but as i woke up the day of the final layout i just decided to do it in Word.
Re: Neovim
#349Earlier quoted context omitted.
"I'd really love to see a richer UI with proper support for features like variable-width fonts." Would the variable-width fonts be simply for display with plain text being edited and buffered, or do you wish to be able to have rich text formatting within the editor (e.g. italic, bold, smart quote marks &c)? Just interested: rich text formatting has been suggested for emacs I recollect.
For display purposes, yes. I want better text readability when I'm working on an article. A nice variable-width font, more line spacing, etc. I want my Vim buffer to look as good and be as comfortable to read as a native text editor like Byword. For formatting, I mostly use Markdown. Ideally, I'd like to see the literal markdown for the paragraph under the cursor, but formatted text for the rest of the buffer. There'…
I can see what you mean, although the flicking between markup and formatted text as you moved the cursor would annoy the hell out of me I think.
Now, would the cursor be a block over a character or a caret between characters? A lot of history riding on that one.
Jef Raskin's Canon Cat springs to mind with its in-place commands (but not Vim's modefulness).
Re: Neovim
#350I would love to have Bram Moolenaar's input on this project.
I've just sent an email to the vim_dev@googlegroups.com mailing list. I asked his opinion on the Neovim project. The subject for my email is "Neovim", so let's wait and see what his opinion is.