10 ms·
Neovim's Next Feature Poll
- rektide 13y agoTerrified that multi-cursor would be for the case of "one user/keyboard/mouse." I'd love to see a Vim that actually does multi-seat.
- deleted 13y ago[deleted]
- seren 13y agoHas anyone used neovim yet ? Is it usable ? Is there any new features or are they only refactoring under the hood ?
- gitaarik 13y agoI tried it. For now it just behaves the same as normal Vim. Most of the work done is indeed under the hood. They are refactoring the codebase so that it will be easier to create plugins, extentions and to use Neovim inside other apps.
- metrix 13y agoIt seems to be in a working state, and loads VERY fast. But I haven't tried modifying the nvimrc or use plugins.
- justinmk 13y ago> For now it just behaves the same as normal Vim Not quite. Neovim has working job control ("async"): http://pastebin.com/hpiCP9Ae http://pastebin.com/hpiCP9Ae It works like the javascript event loop, so even though Neovim is still single-threaded, you can dispatch to external processes and handle the results in a callback(s).
- joelthelion 13y agoI think they should focus on refactoring the core and letting people add features through plugins.
- gaving 13y agoLoving the progress of Neovim so far, even better that notable plugin authors (https://github.com/neovim/neovim/issues/622#issuecomment-41552522 https://github.com/neovim/neovim/issues/622#issuecomment-415...) are getting involved.
- jitl 13y agoI've always wanted to write Vim plugins, but Vimscript and the RPC contortions always looked too hairy for me to get involved -- I'm excited for the new vim-embedding interface so I can get real VIM compatibility with my IDEs.
- pekk 13y agoWhat do people have against Bram Moolenaar? Vim is good already without a coup.
- hedwall 13y agoNeovim has not been started to spite Bram, why would you think that?
- SeoxyS 13y agoHow could they make a sublime-style code minimap in a CLI app?
- martius 13y agoThey are willing to make it more like gvim, running in a separate window, and one of targets of neovim is to use a modern graphics backend to achieve that.
- deckiedan 13y agoNonsense, mate. https://groups.google.com/forum/#!topic/neovim/hTPKGGzwWKA https://groups.google.com/forum/#!topic/neovim/hTPKGGzwWKA neovim is sticking with the standard fixed terminal as the 'main interface', but is building a better/easier way to communicate with external processes. That way a non-terminal Vim plugin can open up extra windows for minimaps, etc. Ideally, this would mean you could have a vim "server" (for lack of a better term) on your dev VM, or where-ever, and local "client" windows on your actual workstation which displays beautiful helptexts, minimaps, code trees, etc.
- jeremyjh 13y agoIt's later in the roadmap but Neovim will also run as a headless slave for use in new GUI applications.
- martius 13y agoOh, obviously I read the bountysource[1] description too quickly when they published it, thanks for the correction. [1] https://www.bountysource.com/teams/neovim/fundraiser https://www.bountysource.com/teams/neovim/fundraiser
- kachnuv_ocasek 13y agoThe goal (as I understood it) is to separate back-end and front-end. That is, you could have a CLI front-end with just text interface, or a GUI front-end with all the fancy features.
- threatofrain 13y agoI've heard from a HN commentator that Neovim has given up on its principle goal of refactoring, and that progress has largely been due to uncrustify. Can anyone else speak to the health of the project?
- deckiedan 13y agoI've been skimming the newsgroup(s) and browsing the commit logs for the past few weeks. It is definitely progressing. I think they didn't quite realise how many people were going to want to be part of it, during the fund raising, and so a lot of effort has gone into coping with the large amount of work from multiple people, merging in patches from the 'main' VIM trunk, etc. There's been a huge amount of pruning - which is still on-going - of old deprecated stuff. For instance, the X11 interface stuff is being simplified (for now) into just the GTK interface. The original author of the neovim concept (Thiago) just posted: https://groups.google.com/forum/#!topic/neovim/R_jXItMXN4E https://groups.google.com/forum/#!topic/neovim/R_jXItMXN4E saying that now he actually has someone to take over a lot of the community stuff, which should free him up to work hard on some of the original actual coding fundraising goals - which is excellent. In some ways, thinking about it, it's probably good that he delayed it, as it means that there's been a lot of extra eyes going over the code of the whole project cleaning things up so that the new features aren't going to conflict too much with other bits being removed. There's one of the guys who's a vimscript genius working on the lua/vimscript side of things, which will get merged in at some point once it's ready. It's essentially a completely separate project until it's ready though. I suspect the first of the big project 'features' to be done will be the libuv stuff - which again, will have little to actually see as a user. Once that's done, and then the lua scripting stuff is done, after that then new features are possible. Even now, though, the difference in the code is dramatic, and it's constantly getting minor cleanups and improvements along the way.
- kansface 13y agoHave a look for yourself: https://github.com/neovim/neovim/commits/master https://github.com/neovim/neovim/commits/master. The code base is now about half of the original size (removed support for legacy OSes, swap all native IO abstractions for libuv, removed dead code, etc). They also split the 25Kloc files called things like misc2.c into multiple files and neovim uses cmake instead of a slew of hand written make files with two decades of commented out hacks. Work on a vimscript -> lua compiler (https://github.com/neovim/neovim/pull/243 https://github.com/neovim/neovim/pull/243) is underway as well as the new RPC plugin stuff (https://github.com/neovim/neovim/pull/582 https://github.com/neovim/neovim/pull/582).
- mikaelj 13y ago"Sublime minimap" and "better autocomplete" are features that use an underlying API. I'd prefer if they could be renamed to "Fetaure X which enables e.g. sublime minimap" and dito for autocomplete.
- davis 13y agoThanks for the feedback. I created the poll so I'll be sure that when we create the Bounty we are clear in that the underlying API is what we are looking to improve.
- mikaelj 13y agoI don't follow - it is /not/ clear to me which underlying API it is that will get implemented by voting for "sublime-style mini-map".
- davis 13y agoPossibly this will answer your question? http://www.reddit.com/r/vim/comments/1yqqhl/bram_responds_to_neovim/cfmxjb9 http://www.reddit.com/r/vim/comments/1yqqhl/bram_responds_to...
- mikaelj 13y agoI did not ask a question - I wanted the poll to clarify what architectural changes were to be made in order for the minimap feature to exist. :-)
- hk__2 13y agoThere’s a typo in the news title: it’s “poll”, not “pool”.
- Galanwe 13y agoIf that's not a command line application anymore. What's the point of keeping the "vim" name apart from teasing users? Call it neogvim or neogvimlikenotepadforjsfullstackdevelopper
- adamors 13y agoYou're free to continue using Vim, no one is taking that away from you. And if you would bother to read up on the project, you'd see that one of its primary goals is to separate the actual editor from the visual interface. That way, everything that is GUI related is separate.
- dasil003 13y agoDo we know how Bram feels about Neovim and whether he is willing to get behind it if it succeeds? The reason I ask is because one of the primary reasons I made the switch to Vim from TextMate is ubiquity and longevity. In the age of GitHub, fads, forks and abandoned projects have become all too common. Meanwhile Bram has proven himself to be a pillar-like benevolent dictator for decades, and to me that means a hell of a lot.
- bpierre 13y agoQuoting his answer [1] in the vim_dev mailing list: It's going to be an awful lot of work, with the result that not all systems will be supported, new bugs introduced and what's the gain for the end user exactly? Total refactoring is not a solution. It's much better to improve what we have. Perhaps with some small refactorings specifically aimed at making Vim work better for users. [1] https://groups.google.com/d/msg/vim_dev/x0BF9Y0Uby8/94tmiaBvFOgJ https://groups.google.com/d/msg/vim_dev/x0BF9Y0Uby8/94tmiaBv...
- mikaelj 13y agoThe refactorings thus far have been specifically aimed at making Neovim work better for /developers/. Which in turn will make it better for the users. A very good way of thinking.
- CyberMuz 13y agoHe is not very enthusiastic about it. Here is his comment about Neovim from two months ago. I don't know if he changed his mind in the meantime. https://groups.google.com/forum/m/#!topic/vim_dev/x0BF9Y0Uby8 https://groups.google.com/forum/m/#!topic/vim_dev/x0BF9Y0Uby...
- aidos 13y agoI've only seen his original post on it [0] - not sure if anything had changed since then. For selfish reasons I'm behind neovim but I can see that it puts Bram in a bad position, which is unfortunate. He's done so much work for all of us (vim users), and ultimately this project just adds to the work he has to do (and makes it even more thankless). He'll be dealing with incompatibility issues between plugins trying to support both systems. Ultimately, I guess he'll have to make a choice as to which codebase to support, by choosing neovim he's deserting everyone on esoteric systems. I think that may be the best outcome; Neovim becomes the new standard, Bram switches over and leaves vim to die. But then what control does he have? It's one of those situations, it seems like a good idea, and could be a massive net win. Then again, it could also really destroy the project. [0] https://groups.google.com/forum/m/#!topic/vim_dev/x0BF9Y0Uby8 https://groups.google.com/forum/m/#!topic/vim_dev/x0BF9Y0Uby...
- chroma 13y agoI am convinced that Vim's greatest asset and risk is Bram Moolenar. Bram is a talented, experienced developer, and I commend him for creating Vim. But he is the only person with write access to Vim's codebase. The primary author of NeoVim is Thiago de Arruda. Thiago tried to work with Bram, but was rejected.[1] Patches similar to Thiago's have been proposed before, but were also rejected.[2] It is for this reason that Thiago has forked Vim, and I wish him luck. It's important to remember that everyone involved is trying to improve Vim as they see it. I think this is a prime example of how the benevolent dictatorship model can fail. 1. https://groups.google.com/forum/#!topic/vim_dev/65jjGqS1_VQ https://groups.google.com/forum/#!topic/vim_dev/65jjGqS1_VQ 2. https://groups.google.com/forum/#!topic/vim_dev/-4pqDJfHCsM%5B1-25-false%5D https://groups.google.com/forum/#!topic/vim_dev/-4pqDJfHCsM%...
- omaranto 13y agoDo users mind that in your words Moolenar is a risk to vim, though? Are people specifically interested in the advancement of vim or just more generally in the progress of vim-like text editors, in which case they can happily switch to neovim if it becomes better than vim?
- deleted 13y ago[deleted]
- scott_s 13y agoBased on the results of his labor: he produced a stable piece of software that millions rely on every day. Myself included.
- deleted 13y ago[deleted]
- scott_s 13y agoThat is not the results of his labor. That is the means by which he achieves those results. There is an enormous difference. You're assessing the technical state of his project, and confusing that with its actual impact on the world. They are two different things. I call him a "talented developer" because he has successfully developed and maintained (for two decades) a stable piece of software that is the base infrastructure on millions (billions?) of computer systems around the world. Millions of other developers rely on his work for their own work. I'll grant that maybe he has done this despite his engineering skills. But his software is a success by any reasonable measure, and I think it takes talent to achieve that. I love code. I get an enormous pleasure of well engineered code. I appreciate code for its own sake. But code also serves a purpose, and I refuse to believe that someone whose code is so enormously successful somehow did so by accident, without talent.
- edanm 13y agoPlease, please implement multi-cursor support. For anyone that doesn't agree, please read my previous post on HN on the topic: https://news.ycombinator.com/item?id=1625382 https://news.ycombinator.com/item?id=1625382 I wrote to Thiago about this already, but we don't even need multi-cursor support - just a few additional hooks so we can implement a multi-cursor plugin. Although to be honest, making it part of core is vastly preferable, since it is a hard feature to get right (e.g., how do you deal with copy-pasting into multiple-cursors)?
- hk__2 13y agoWhat problems can you solve with multi-cursors that you can’t with actual features like block selection?
- weaksauce 13y agoEditing the same thing in different places at the same time.
- prawks 13y agoIf it's the same thing, find & replace? Just playing devil's advocate, I've never come across a situation where I wanted multiple cursors that sed or macros couldn't do for me.
- weaksauce 13y agoI don't particularly need or use the feature over block selection or find and replace but it's similar to an interactive find and replace where you don't need to edit every instance of the found term. Some people love it.
- edanm 13y agoSimple (very common example): <pre> .some-css-rule { padding-left:50px; padding-right:50px; } </pre> Say I want to edit those two numbers. With multi-cursors, it's as simple as select one number, hitting a button that causes the other number to be selected, then writing the new value. Now, after I wrote it, I realize I forgot to put a space after the colon, and want to change the formatting. No problem - I just make the change to the first line, and the next line follows. Same as macros? Kind of. But let's say I make a mistake in the macro, e.g., I move the cursor left to the beggining of the line letter-by-letter instead of hitting "home", which is a killer for a macro since each line is a different length. (this is a contrived example a real vim'er will never do, but there are plenty of real examples of 'oops forgot about that' things when recording macros). Anyway, when I run my macro, suddenly things won't work, and then undoing and starting the re-record process takes time. But if I'm doing this with mulitple-cursors, I see right away, visually that something's wrong, and it's easy to fix - I just hit "home" after moving the cursor left. And note - this is a drop-dead-simple use case that happens 10's of times a day for any css programmer. Similarly, most programmers will run into cases where they have two similar if blocks one after another, or two similar "except" blocks, and so on. And that's not even going into lots of other, very powerful cases, like taking a function that gets a list of paramaters, and being able to easily manipulate these paramaters, e.g. given "foo(a, b, c, d, e)", I can easily multi-cursor all the commas, then copy all the params, then paste them after the func definition, hit enter, and I've got a list of all the params after the function definition. And this isn't hard, at all! I visually see everything I'm doing as I do it, and if something goes wrong, I fix it on the spot. I could ramble more about this, but I think I've either convinced you I'm crazy, or at least to try multi-cursors out :)
- indralukmana 13y agoSo anyway, where is NeoEmacs? *i am going to run now.
- cube_yellow 13y ago"NeoEmacs" is guilemacs, putting emacs ontop of the guile vm. look at the GSoC project.
- indralukmana 13y agoOh, i just learn about this. But when i search google for this guilemacs there are no definitive information for this project (as in where i download the program?). So based on my little browsing, vim and emacs have some kind of different problems? (or are they even problems?) Vim has the benevolent dictator who prefer supporting backwards compatibility to developing features. And Neovim try to address that. Emacs is using a "hacky emacs lisp" and "guile emacs" tries to incorporate a scheme based improvement on the backend.
- gcao 13y agoHas anyone created mapping to jump AFTER a character? I did it and think it is great.
- manolus 13y agoThe greatest thing implemented in neovim, IMHO, is this feature: https://github.com/neovim/neovim/pull/475 https://github.com/neovim/neovim/pull/475
- afarrell 13y agoOthers have probably already said this elsewhere, but I think high quality error messages for vimscript (or the lua api) are one of the most important things. The project already cares about the developer experience for people writing plugins. Error messages are a difficult but important part of that.
- rat87 13y agoI feel like one of the main goals of neovim is to make it more like emacs. Or guile emacs. Instead of a shitty language for plugins and configuration: vimL (with some support for plugins in alternative languages but not well integrated and not present in all vim installations) and replace it with a good interface to a single language. Like emacs. Much of emacs is written in elisp instead of c, I wonder if this will enable quicker/higher level development with lua for parts of neovim. The plans for a compatibility interpreter for vimL on top lua sound a lot like the elisp on top of guile plan for guile emacs, and isn't one of guile emacs goals to add support for concurrency?
- wirrbel 13y agoBoth vim and emacs have had problems recently in balancing refactoring needs and their traditional architecture and project layout. People are more and more used to contributing to projects with an occasional pull request. However to benefit from this, the projects have to become more accessible to these people. This makes all those changes that are introduced to neovim necessary. If tests are already beneficial for a developer who has written the codebase, the occassional contributor really depends on them. Vim and emacs are projects that are of special strategical importance to the world. They must not vanish.
- js2 13y ago"pool" vs "poll" - can the submission title be corrected?
- Simucal 13y agoThiago claims that one of Vim's biggest problems is its lack of testing infrastructure. It is difficult to refactor or make changes without the chance of introducing some possibly obscure regression. This is probably a big part of Bram's reluctance to merge large changesets from other developers. I honestly thing if he can successfully pull off this "msgpack UI" and get a solid set of tests written (which the community seems eager to start work on) this project will be a huge success. Here is his quote from the mailing list: "This may not be so obvious, but vim's biggest problem has nothing to do with the lack of the above features. It's something much more basic: poor testing infrastructure. While vim has some automated tests(about 200 counting with the ~100 tests embedded in test 49) those only catch the 'biggest' bugs, with many small ones being introduced by patches and only detected at a later time. It's a true maintenance hell, and here's a post on reddit that illustrates the problem(even though the author himself disagrees with neovim): http://www.reddit.com/r/programming/comments/1yjzez/neovim_a_project_to_refactor_and_modernize_the/cfla7j5 http://www.reddit.com/r/programming/comments/1yjzez/neovim_a... The problem is that in it's current state, vim cannot grow because there's no easy way to write automated tests for it. The current test suite is very hard to understand and those that submit patches probably won't write tests because it's too complicated. But patches need to be tested, especially bug fixes which must acompany a regression to ensure they won't be reintroduced. So it's easy to see why Bram is skeptical about merging patches, especially new features: He has no way of knowing if those patches will break existing code. In the example given by the reddit comment, Bram 'solved' the problem by simply picking the lesser of two evils. This is one of the firsts issues neovim aims to fix: By writing a msgpack 'UI', we'll be able to write well-documented functional tests in a high-level language. Contributors reporting bugs will be able to reproduce them with a test cases and new features will be properly tested. As the test suite covers more code, neovim will be more 'protected' since there will be a bigger chance of catching bugs the minute a PR is sent(with travis). People need to understand that before posting issues regarding new features or new ideas, as neovim must be properly 'secured' against bugs first."
- wirrbel 13y agoThe whole approach makes a lot of sense. Successful refactoring goes hand in hand with setting up a test environment. Code that is not covered by unit tests is legacy code. Without tests, you have to fear breaking things and fear is a bad starting point for development. I backed Neovim and I really hope that it succeeds. I think the Vim codebase is criticized a little too harshly in general. It is a child of its time. Whether Lua is the optimal choice as an extension language remains to be seen, yet it is a very pragmatic choice and over time we will see that the C core of vim will shrink dramatically. I seriously hope that Bram Molenaar is not offended by the fork (and I think he is not). For the vim community having neovim as an independent development line will have its merrits until it is clear whether the fork can replace the proven editor.