I feared it would be written in javascript (it's on the front page of HN after all), but I was very positively surprised.
There are projects where it's not appropriate to use node.js and the hell it comes with.
Vis: A Vim-Like Text Editor
51–60 of 166 posts
Re: Vis: A Vim-Like Text Editor
#52More people should definitely try out sam and 9term as examples of how much code/features you don't really need and can still get real work done. Personally, I wish sam had even less complexity and features than it currently does and thus be more understandable and hackable. Also, never going back to a normal terminal again, "dumb" terminals are awesome. And actually, this experience has lead to a philosophy of softw…
As much as I love visualizing my code with Intellij, the thing is huge and clunky. Nothing beats the simplicity of Sublime and the good'ol Terminal.
Unless it's vim and the good ol' terminal. :-D
Re: Vis: A Vim-Like Text Editor
#53More people should definitely try out sam and 9term as examples of how much code/features you don't really need and can still get real work done. Personally, I wish sam had even less complexity and features than it currently does and thus be more understandable and hackable. Also, never going back to a normal terminal again, "dumb" terminals are awesome. And actually, this experience has lead to a philosophy of softw…
There are some "political" aspects too, in that AI and VR aim for maximal resource consumption—the more power, the cooler.
Re: Vis: A Vim-Like Text Editor
#54I feared it would be written in javascript (it's on the front page of HN after all), but I was very positively surprised. There are projects where it's not appropriate to use node.js and the hell it comes with.
Can we please try to stop talking about this specific language ecosystem as an awful deplorable hell hole or whatever?
Re: Vis: A Vim-Like Text Editor
#55Earlier quoted context omitted.
Reposting an answer from a related thread. The main difference is that vis is written from scratch while neovim inherited an old and hard to maintain code base. This allows vis to experiment with various ideas: - native multiple cursors/selection support - structural regular expression support - different core data structure resulting in efficient large file support - LPeg based syntax highlighting - Lua as an in pro…
Great! I remember last time I looked at Vis it wasn't so far along (it had no Lua integration AFAIK). When I started submitting code to Neovim my biggest desires for it were (1) Lua extensibility (2) A clean codebase (3) Compatibility with (most) Vim plugins. Perhaps ZyX-l's Vim to Lua project (for Neovim) could help with (3) at some point, if that's desired. An LPeg based syntax highlighting was also something in th…
Does this kind of PEG parser deal somewhat decently with partial or incorrect syntax trees?
Re: Vis: A Vim-Like Text Editor
#56One of these days, I'm going to sit down and try out this, emacs-evil, and neovim. Side-by-side. Need to figure out which one I like most.
I just switched from vim to neovim to evil. I can't see myself ever going back. (Neovim was basically just vim with async support, and terminals, but as a tmux user, that didn't really grab my attention).
There's a lot more polish in the integrations for emacs than vim, likely as a result of literally everything in the editor being a function call that can be hooked into.
The only thing I miss is solid tab functionality (there's a short of hack I've seen so far, but feels too rough for me). But honestly, with projectile + heap, I barely miss that.
Company-mode far outpaces the auto completion options in vim (though to be fair to the plugin authors, apparently they need to resort to major hacks to perform some of the things they do). Just as an example, when you autocomplete a function call, it populates the arguments and let's you tab through completing them. This same functionality sits as open tickets in the major vim autocomplete plugins, with a response of essentially "this is really hard to do in vim, hopefully we can figure something out in neovim".
It's worth the 2-3 days to make the switch and set yourself up. Also, a recommendation -- autostart emacs in server mode and use enacsclient to connect to that for all your editing needs.
Re: Vis: A Vim-Like Text Editor
#57Earlier quoted context omitted.
> I wonder how easily this can be recreated using a Lua plugin. It's probably a better idea to use tmux/screen/dtvm for terminals rather than embedding a terminal in a minimal editor. The TODO list mentions asynchronous event loops, that's necessary to do any plugins with external processes neatly.
Well. Having a terminal as a buffer makes it possible to copy/paste into/from the terminal. Also autocomplete from all the buffers is working. It's really convenient. And implementing a repl integration is trivial.
You can also make a command that inserts a file into the current tmux buffer, which is technically a much more straightforward solution than reimplementing terminal emulation, I think.
Re: Vis: A Vim-Like Text Editor
#58Excellent. The more vim the better. I would like to see many of the core vim patterns replicated in other editors: - modal over chords - text objects - the vim "language" which ties it together - all the other good stuff, did I mention text objects ? There is a reason vim has more users today then ever before: once you learn the deceptively simple language you can have deep conversations with your editor.
I am very glad that most IDEs have either native or plugin based vim-modes.
Re: Vis: A Vim-Like Text Editor
#59I feared it would be written in javascript (it's on the front page of HN after all), but I was very positively surprised. There are projects where it's not appropriate to use node.js and the hell it comes with.
Can we please try to stop talking about this specific language ecosystem as an awful deplorable hell hole or whatever?
It's not node.js that's horrible: it's great for what it does (web development). When taken out of that use case, it's awful, because it's simply not meant to do systems programming or to make local applications.
It's kind of like people who knock Perl: it's made specifically for text parsing, nothing more, and too many people use it for much more. Since it's not meant for more complex things, it fails, understandably.
I think what the comment was trying to point out is that oftentimes there are things on Hacker News that are written in JS that shouldn't be: systems programs, emulators, shells, etc. This is not the fault of the ecosystem itself, but rather the misunderstanding of the authors about the viable use cases of the tool that they're using (node.js).
Re: Vis: A Vim-Like Text Editor
#60More people should definitely try out sam and 9term as examples of how much code/features you don't really need and can still get real work done. Personally, I wish sam had even less complexity and features than it currently does and thus be more understandable and hackable. Also, never going back to a normal terminal again, "dumb" terminals are awesome. And actually, this experience has lead to a philosophy of softw…
9term/Unix is still not as lean as something you'd get with a more integrated environment like Oberon or Lisp. Just think of the many ways of parsing arguments and input. Ad-hoc languages wherever you look.