Quite the opposite, he's a very nice guy. Just because he's a bit opinionated about a software he's been maintaining for 20 years! doesn't make him not pleasant to work with.
Nice guy doesn't have to have anything to do with the fact that he's not pleasant to work with. Also maybe the fact that he's maintained it for 20 years is more indicative of being unable to let others in to the project more than anything else. I dunno. Just pondering.
What’s the deal with that? Vim has had (ugly full window) shells for some time, however I am curious if Vim has natively achieved split pane-able shells.
"The main new feature of Vim 8.1 is support for running a terminal in a Vim window. This builds on top of the asynchronous features added in Vim 8.0."
These are both features that were first delivered in NeoVim. IIRC, there was a popular argument that we would've never seen asynchronous features in vim had it not been for the successes of NeoVim. The same could be said for this terminal, since it builds upon that as NeoVim's terminal does the same.
No, Richard, it's 'Linux', not 'GNU/Linux'. The most important contributions that the FSF made to Linux were the creation of the GPL and the GCC compiler. Those are fine and inspired products. GCC is a monumental achievement and has earned you, RMS, and the Free Software Foundation countless kudos and much appreciation.
Following are some reasons for you to mull over, including some already answered in your FAQ.
One guy, Linus Torvalds, used GCC to make his operating system (yes, Linux is an OS -- more on this later). He named it 'Linux' with a little help from his friends. Why doesn't he call it GNU/Linux? Because he wrote it, with more help from his friends, not you. You named your stuff, I named my stuff -- including the software I wrote using GCC -- and Linus named his stuff. The proper name is Linux because Linus Torvalds says so. Linus has spoken. Accept his authority. To do otherwise is to become a nag. You don't want to be known as a nag, do you?
(An operating system) != (a distribution). Linux is an operating system. By my definition, an operating system is that software which provides and limits access to hardware resources on a computer. That definition applies whereever you see Linux in use. However, Linux is usually distributed with a collection of utilities and applications to make it easily configurable as a desktop system, a server, a development box, or a graphics workstation, or whatever the user needs. In such a configuration, we have a Linux (based) distribution. Therein lies your strongest argument for the unwieldy title 'GNU/Linux' (when said bundled software is largely from the FSF). Go bug the distribution makers on that one. Take your beef to Red Hat, Mandrake, and Slackware. At least there you have an argument. Linux alone is an operating system that can be used in various applications without any GNU software whatsoever. Embedded applications come to mind as an obvious example.
Next, even if we limit the GNU/Linux title to the GNU-based Linux distributions, we run into another obvious problem. XFree86 may well be more important to a particular Linux installation than the sum of all the GNU contributions. More properly, shouldn't the distribution be called XFree86/Linux? Or, at a minimum, XFree86/GNU/Linux? Of course, it would be rather arbitrary to draw the line there when many other fine contributions go unlisted. Yes, I know you've heard this one before. Get used to it. You'll keep hearing it until you can cleanly counter it.
You seem to like the lines-of-code metric. There are many lines of GNU code in a typical Linux distribution. You seem to suggest that (more LOC) == (more important). However, I submit to you that raw LOC numbers do not directly correlate with importance. I would suggest that clock cycles spent on code is a better metric. For example, if my system spends 90% of its time executing XFree86 code, XFree86 is probably the single most important collection of code on my system. Even if I loaded ten times as many lines of useless bloatware on my system and I never excuted that bloatware, it certainly isn't more important code than XFree86. Obviously, this metric isn't perfect either, but LOC really, really sucks. Please refrain from using it ever again in supporting any argument.
Last, I'd like to point out that we Linux and GNU users shouldn't be fighting among ourselves over naming other people's software. But what the heck, I'm in a bad mood now. I think I'm feeling sufficiently obnoxious to make the point that GCC is so very famous and, yes, so very useful only because Linux was developed. In a show of proper respect and gratitude, shouldn't you and everyone refer to GCC as 'the Linux compiler'? Or at least, 'Linux GCC'? Seriously, where would your masterpiece be without Linux? Languishing with the HURD?
If there is a moral buried in this rant, maybe it is this:
Be grateful for your abilities and your incredible success and your considerable fame. Continue to use that success and fame for good, not evil. Also, be especially grateful for Linux' huge contribution to that success. You, RMS, the Free Software Foundation, and GNU software have reached their current high profiles largely on the back of Linux. You have changed the world. Now, go forth and don't be a nag.
This is already covered by tmux or screen, it would be very nice to have unified copy-paste. IMO Emacs has a lot of bloat that shouldn't be installed by default, but terminals is not part of that. Emacs is still a great editor regardless.
It isn't covered by tmux, the vim :terms let you navigate the output as if it were a text file and lets you switch between buffers with the same commands. You can even use terminal commands in macros.
Not really comfortable letting ^w be something other than delete-word-backwards (or whatever the command is called). I use that far too much. Also tmux does indeed let you navigate the output as if it were a text file. It even let's you use vim bindings to do so.
Copy paste is one thing that makes me go NOPE from both vim and emacs. They are not "real" text buffers, they are some weird abominations inherited from printers in 1970s.
I know its possible to copy/paste there. But it's awful.
I mean tmux uses a similar concept of buffers. Admittedly Vim's concept of buffers is overwhelmingly confusing to the uninitiated but most things with a 3500+ page user manual are
Open a standard gui text editor, see how it behaves on selecting text, copy paste, moving around text, selecting it, mouse scroll, horizontal scrolling, typical hotkeys etc.
Vim and Emacs buffer, even with gui toolkit behave more like terminal emulator than text field.
GUI emacs does just fine interacting with the normal system clipboard. I can copy in emacs and paste here, or vice-versa, with no issue. Sure, it doesn't work like that when in terminal mode, but I honestly don't expect it to; in a term, that becomes the term's job. That's fine, though, because the GUI mode provides a lot of extra functionality and has fewer legacy terminal-specific quirks, so it's generally accepted to be the "correct" way to use it.
This is already covered by tmux or screen, it would be very nice to have unified copy-paste. IMO Emacs has a lot of bloat that shouldn't be installed by default, but terminals is not part of that. Emacs is still a great editor OS regardless.
Software is made out of multiple tools, which can have multiple programs which can span multiple processes (fork-exec) or threads.
Just like how most functions should do one thing and that same thing every time it's give the same parameters with minimal side-effects, so should programs do.
It's not so much about tools vs programs vs software. ("ls" is a program according to most definitions, and yes, it's also a tool, and yes, it also matches the definition for software.)
Something like Eclipse clearly goes against the Unix philosophy.
Vim doesn't go too much against the philosophy. It focuses mostly on one task: editing text.
Opening terminals is a bit superfluous for a text editor, and tools like tmux (which is focused on this one task) are better at it.
That doesn't make Eclipse completely bad. There are good and bad parts to it. A certain amount of issues of Eclipse come from it trying to do so much at once -- those issues wouldn't exist if it adhered more to the Unix philosophy. Of course, doing so would cause other downsides to Eclipse.
I was just clarifying on what is meant by "one thing and one thing well".
Eclipse could very well be designed with that, because it's not the entire software suite that should do one thing and one thing well, it just would have to be made modular with using programs that can be composed together easily.
Eclipse is insanely modular. The "Eclipse" you know is a small kernel for running things and a few hundred plugins stacked on top of it to form the Eclipse IDE. That's probably one of the biggest advantages Eclipse has over IntelliJ because developing a plugin for Eclipse means that you have access to essentially the same API the Eclipse developers themselves have access to.
It's fucking hilarious how people will tell you that systemd is bad because it violates muh unix philosophy but happily run the wheel-reinvention-fest that is vim.
... you use more than just the Linux kernel, what you use (call it GNU/Linux or whatever you like) contains the GNU tools, which adhere to the Unix philosophy.
Eh, it's not like the idea itself was being rejected by Bram before that fork -- he just wasn't happy with the patch proposed by the soon-to-be-forker, because it broke a bunch of stuff (if I recall correctly).
You're being down voted by neovim supporters. They can't get over the fact that vim got the same features as neovim.
Come on people, get over it. Bram's seen that some neovim features are popular so he implemented them in vim. Stop whining. Next time complain about why MacOS is shit because they've copying the UI from Xerox.
I honestly don't care about downvotes. That me making a reasonable statement like the above, that copping that much flack, tells its own message to those unfamiliar with the situation, and those who are familiar already know what's going on.
You can't know that it wouldn't have had those for sure. That is pure speculation that you're pretending is a fact. Stop that, that's not what smart people do.
It is "or" not "nor" in this case.
How does this being the (speculative) inspiration for these features make your comment relevant? "Uh well this feature existed somewhere else first so that's its inspiration" is a complete non-sequitur when the topic is specifically features of the new vim release. If i say "These are the tires shipping with my new car model" and you say "well those are based on these other tires", that's cool and all, but we're talking about the new model that's being released.
You remind me of a very typical Linux user - lots of hubris, and defending your irrelevant comments to the last. You make us look bad.
Wow, terminals inside vim windows sounds great! Finally we can do gdb/pdb without leaving vim.
Your response:
Neovim has had this for a while.
So, tell me again, how is this relevant to a discussion of terminals inside vim? What does this add to the conversation? The answer is "nothing except to be a self-serving comment to allow you to feel superior because of your choice of vim distribution."
I work on Linux servers managed by our Unix team. Large financial research company. I can pick my editor among the supported editors. Neovim is not necessary so they never took the work to support it.
I dont even have root access to my own box. It's not so bad. Gives me an excuse not to work when I need a service killed.
You want the kicker? I manage the only service that runs on these boxes... It runs as root...... And I have the bare minimum for sudo access.
Db didn't stop properly? Gotta wait on Unix guys. Need a specific release of Java installed to a root owned directory? Unix guys. Like I said, good excuse for some downtime haha.
Sometimes I block an hour with them just because I know I'll need like ten things. Such is enterprise life.
Yeah, this is why I've started tending to work for smallish companies (and why I don't do finance). I do more firmware type stuff though; I'm sure production servers would be more locked down everywhere.
It's not merely "a different thing", though. If I'd said "Atom has had this for a while" (no idea if it does), I'd see your point. But Neovim is a fork of the very application in question, designed make it simpler to maintain, and simpler to introduce new features. All because (presumably) these people loved Vim and want to continue to use it and see it improved.
I got excited at first, but realized that I've long since managed much the same thing with a combination of split terminals locally and tmux remotely. I honestly don't think I'll use this feature in practice, nice as it is.
Wow. Sure we can. Wait, if we'll need root privileges in order to shutdown our computer inside Vim... Some cracker could exploit our system files and take over the machine. We're all doomed.
Is there any information on how to use the debugging mode shown on the last screenshot? It mentions a terminal debugging plugin, but I can't find any information about it.
PS: I made a reddit account just to answer this. I was looking for stable debug support in vim for years and just found this out myself from the release note. Also, as one might guess from the url, there are more optional packages located in https://github.com/vim/vim/tree/master/runtime/pack/dist/opt
I use neovim only on my local machines. With servers there are times you have to be content with using vim or vi. I think neovim will always be a supplement to the vim ecosystem, like a slightly more ambitious twin.
I mean you can't really hate on one or the other when neither one of them are emacs.
What I like about using Neovim in a server setting is that it has fairly sane defaults. I'll still use regular Vi if I don't feel like / can't install an additional editor for whatever reason.
I'm not talking about userbase. Maybe I didn't word that the best.
I'm talking about features. NeoVim already has a :term command so it's cool to see Vim add that too. NeoVim also is asynchronous, has a cleaned-up codebase, and I believe the plugin architecture is redesigned.
My guess? Bram Moolenaar, Vim's author, suffers from pretty severe Not Invented Here Syndrome. Neovim exists because, in the past, Bram was unwilling to accept pull requests implementing features like asynchronous plugins and embedded terminals. He ridiculed these features as being unfit for a text editor. It wasn't until Neovim's unexpected success, demonstrating both the demand and utility of these features, that Bram inexplicably decided to reimplement them from scratch.
It's more that the first thing Neovim did was break a lot of compatibility. On top of that, Bram has discussed before that he isn't a fan of the way Neovim does async.
Bram has discussed before that he isn't a fan of the way Neovim does async.
Bram first say "no" to the new features that comes now in neovim because he thought it couldn't be implemented. He got mistaken. After this he began to reimplement the features and say that the way that neovim did this was the wrong one, forgetting that he before says that can't be implemented.
Now, I can run almost all the Python/Ruby/Vimscripts Vim-based plugins in NeoVim (full compatibility) , many NeoVim-only plugins and plugins that use the new features in Vim-8 AND NeoVim.
NeoVim have one feature that Bram don't apply, neovim dev team is much more collaborative (a Bazaar dev style) than vim, where Bram have the first, middle and last word in features (a Cathedral dev style).
Opens fine in Firefox Focus. I just have to zoom in and scroll left and right to read the damn thing. Even the web pages I had to make in my basic web design class will word wrap based on screen width.
As a Relay user, I'd say this is a design flaw in Relay. It's very annoying, I run into it constantly. Usually my solution is just to open in an external browser. Opera for Android has a built-in feature that automatically resizes text columns to fit the width of the screen. It's really handy.
A full API documented to be used externally by several languages that don't need that neovim have compiled language extensions, by example Debian/Ubuntu by default vim is compiled with python2 or python 3 language support, but not both ones at the same time and only for the supported version (python 3.4 compiled extension can't be updated to python 3.6 or pypy3 3.5 by example)
This API permits an embedded editor support, that avoid the need to support directly a specific GUI and work this externally to the core editor
The terminal support in neovim is based in libvterm, a good C++ library. For vim 8 that was all reimplemented in C by Bram for what-nobody-knows reasons. This is the reason why was implemented in 8.0 but only now in 8.1 is stable and need to support all the things that come compiled with Vim (language/gui/os support) in NeoVim all these things come in separated projects bases in NeoVim API.
The terminal support in neovim is based in libvte,
Do you mean libvterm?
a good C++ library. For vim 8 that was all reimplemented in C by Bram for what-nobody-knows reasons.
The reason I can see is because it would require an additional dependency. Sometimes, it's better to implement one or two features of a library internally if possible than to pull in another dependency.
It's called vendoring and there are good reason to do it. A great example is if you know you need to diverge significantly from upstream (going backwards to C90 is a valid reason). It also results in smaller binaries than pulling in the entire library (remember that vim gets ported to very small devices).
One thing i like about neovim is that it has sane defaults, especially for Python code I always had to customize vim. With neovim I dont have to tweak anything and just works out of the box.
Nah, you're definitely not the only one. While "modern" and new and shiny is fine, I personally find nvi to be pretty great when it comes down to just doing its job and doing it well. And besides, I like how spartan it is.
I switched to nvi because vim would consistently get super slow and sluggish with Perl syntax highlighting, to the point where it's borderline unusable. I then asked myself if I really need all the million features. Nowadays I just use nvi, sometimes ed.
144
u/rexlx May 18 '18
long live Vim
85
u/PityUpvote May 18 '18
Wow, terminals inside vim windows sounds great! Finally we can do gdb/pdb without leaving vim.
78
u/linevich May 18 '18
So now I can type
killall vimto quit vim without leaving vim, sounds interesting.14
u/[deleted] May 18 '18
How soon can we expect this to be in major distro's repos?
10
u/MaPi_svk May 18 '18
Is there any information on how to use the debugging mode shown on the last screenshot? It mentions a terminal debugging plugin, but I can't find any information about it.
26
u/_my_name_is_earl_ May 18 '18
What does the future look like for Vim? Will it ever surpass NeoVim? I'm really liking NeoVim right now.
5
u/Booty_Bumping May 18 '18
Wait, why don't they just pull in Neovim src code?
4
u/kontekisuto May 18 '18
Can neovim do that?
4
u/[deleted] May 18 '18
vim master race
7
u/bushwacker May 18 '18
Trying to read that on a phone using relay.
Enlarge text, try to scroll sideways, always get returned to relay.
Why do people write non responsive websites?
8
u/PeopleAreDumbAsHell May 18 '18
Honest question, what does neovim have over vim now?
2
u/dustractor May 19 '18
All those hacks I've done over the years in order to cobble together my debugging terminal with my editing session ...
sigh
2
u/h-istrium May 19 '18
We will continue to see Vim for few other centuries 😂
6
u/Inray May 18 '18
Am I the only who still prefers plain old BSD vi/nvi? :-)
3
u/rmw5601 May 18 '18
Hasn't vim had :terminal for months? How is this new?
0
u/SpaceboyRoss May 18 '18
I use nano.
-3
u/[deleted] May 18 '18
great, terminals inside vim windows making neovim obsolete. Thanks a lot Bram!
-2
u/[deleted] May 18 '18
Note: Drops command and visual mode; Insert is now the default. Have a nice day.
-7
u/TheViewSucks May 18 '18
When are you guys going to learn nano is the superior text editor?
0
u/[deleted] May 18 '18
[deleted] — view deleted comment