This looks very interesting. Are there any advantages to using it as opposed to neovim in a terminal? I guess my question can be posed to any gui text editor. Still, nice project!
I like having gvim or macvim as the default text editor to open files when the are clicked from Dolphin/Finder/etc so that I can read and edit the file with vim and my config, rather than whatever the OS default low power GUI text editor is. Maybe I could rig up something to open a new terminal and then open vim in that but vim in a GUI works quite well.
Eww, a 20MB GIF with harsh dithering artefacts. And then another 22MB in two more GIFs. All in the repository. (a) GIF is not the right format here, use a video format because it’ll produce a visually superior result (proper colour, no dithering needed—not that it actually is even with animated GIFs) and much more usable result (not autoplaying if the user agent’s configuration says not to, allowing scrubbing, showin…
I believe the best practice is to use a dedicated "media" branch for screenshots/gifs/webp. Then you can use them on your readme like this . You can rewrite history on the media branch so the files don't accumulate whenever you update them. I found this idea here: https://medium.com/@minamimunakata/how-to-store-images-for-u...
That’s still going to be included in a standard clone, though at least it makes it possible to do a partial clone and exclude that branch. rjzzleep is right to point out the wiki repository as a good place to store such things, still being a Git repository so that it need not be tied to GitHub, but there’s also the option these days of editing the README in GitHub’s web interface and uploading the images or videos through that, which stores it on GitHub servers outside the repository.
What's up with the huge cursor in insert mode in some of the GIFs[0]? [0] https://github.com/rohit-px2/nvui/blob/main/assets/display/v...
Just above the gif: > Customizable cursor height (see :h NvuiCaretExtendTop and :h NvuiCaretExtendBottom) Ex. :NvuiCaretExtendTop 200, :NvuiCaretExtendBottom 100 (see below)
What's the elevator pitch for Neovim over regular Vim or GVim? I see verbiage about extensibility and modern guis, but has any Vim user actually seen real world benefit after switching to NeoVim? Is it all just icing?
>has any Vim user actually seen real world benefit after switching to NeoVim
I've tried NeoVim for a couple of month this year.
It's a tad snappier than vim, but there are a number of "quirks" (behaves ok, but doesn't behave exactly like vim) that made me walk away from it: at this point, vim is so hard-wired in my brain that any tiny difference in behavior is painful.
What's the elevator pitch for Neovim over regular Vim or GVim? I see verbiage about extensibility and modern guis, but has any Vim user actually seen real world benefit after switching to NeoVim? Is it all just icing?
I am willing to take the philosophical stance that even if NeoVim was only a 1:1 feature parity of Vim, it would still be a GoodThing. We need to find a way to dig ourselves out of endless backwards compatibility and advance the state of software. Supporting 8.3 filenames no longer has its place. This[0] post about the early days of NeoVim development made some interesting points about Vim, but one choice quote I rec…
There has been a lot of talk around here lately about modernizing emacs. It really seems to me that neovim is shaping up to be the new “modern” emacs. With full lua integration, lsp, gui clients, and projects like neorg it’s getting a lot closer to building its own emacs like ecosystem.
> Splits I can drag around to move and resize with a mouse You can already use the mouse to resize splits in neovim, :set mouse+=a > "Native" window tabs instead of terminal-style tabs Which features would "native" tabs provide that aren't already available? > A gvim-style menu bar with some operations for which I can't be bothered to remember the key combination. Which operations would you put under the menu?
I want native style tabs and line numbers. By native style, I mean both of them in some way separate from the main code window. When I have line numbers enabled in nvim and if I select code using mouse to copy, line numbers get selected automatically and only way to get what I want is to use visual mode or turn off numbers. Its a bit slower than selecting with mouse for me
There are lots of great ways to handle this in vim.
You can sync your system clipboard with vim, for example. This also works well with clipboard history apps like Alfred or CopyQ.
Also, :set mouse+=a solves the line number selection issue.
I have not tried this one yet, but what I'd like to see in a nvim gui: - Splits I can drag around to move and resize with a mouse - "Native" window tabs instead of terminal-style tabs - A gvim-style menu bar with some operations for which I can't be bothered to remember the key combination. So, overall, mostly mouse support and better discoverability. I've tried a few though and haven't really found what I'm looking…
> Splits I can drag around to move and resize with a mouse You can already use the mouse to resize splits in neovim, :set mouse+=a > "Native" window tabs instead of terminal-style tabs Which features would "native" tabs provide that aren't already available? > A gvim-style menu bar with some operations for which I can't be bothered to remember the key combination. Which operations would you put under the menu?
> Which features would "native" tabs provide that aren't already available?
In ideal world: reordering, tearing off and merging.
What's the elevator pitch for Neovim over regular Vim or GVim? I see verbiage about extensibility and modern guis, but has any Vim user actually seen real world benefit after switching to NeoVim? Is it all just icing?
I think one of the reasons I switched was being able to have my config in the xdg config spot instead of my home directory. I don't know if oldvim ever added support for that, but both emacs and neovim support it now.
Reading from the v1 release, there are currently only Windows & Linux support. Maybe you could build it from the source code though. (edit) Building for MacOS doesn't seem to work https://github.com/rohit-px2/nvui/issues/20
This looks very interesting. Are there any advantages to using it as opposed to neovim in a terminal? I guess my question can be posed to any gui text editor. Still, nice project!
I've been using NeoVide (same idea) for the last few weeks and I've noticed three differences: the colors/font are closer to the intended look, it's got nice smooth (and quick) animations, and it seems like the rendering is faster than in the terminal to a degree it feels more responsive.