3 ms·

To directly answer your question, MacVim is a GUI wrapper around plain ol' vim. AFAICT, MacVim has no relation to neovim.

ARandomerDude 4y ago
Great comment, I’ll add there’s a MacVim-like GUI wrapper but for Neovim called VimR that i really like. https://github.com/qvacua/vimr https://github.com/qvacua/vimr
- predmijat 4y ago
  There's also Neovide which is written in Rust, which makes it, well, blazingly fast. https://github.com/neovide/neovide https://github.com/neovide/neovide
  - halostatue 4y ago
    Neovide is fast, but does not have any macOS-level integration. While it’s nice that it’s not electron like so many other neovim GUIs, it does not work well on macOS.
    - greggarious 4y ago
      Ugh, no offense but I'll skip neovide then -- I hate stuff that does the crap GIMP does where it doesn't blend in with the rest of macOS
- halostatue 4y ago
  Can't stand it, myself. Of the various Neovim macOS UIs, this is the one that is perhaps closest to MacVim, but the UI choices about having the drawers present all the time and other pieces make it both less reliable and less usable than MacVim itself. That's the main problem with most of the neovim GUIs—they get opinionated about what a Vim GUI should be. First, foremost, and always, it must be vim in a GUI window. Second, it must have native OS keybindings and integration (clipboard, menu, etc.). Finally, it should be able to have possible extensions that work well with existing plug-ins. (I use Fern for my file tree. I don’t need a built-in file tree that is always visible.) They must, at the core, always be vim. This is why I think that Oni2 was a mistake and why it’s one of the few software packages I regret paying. I don’t want vim motion keys with VSCode extensions. I want a Vim GUI.
  - ARandomerDude 4y ago
    I don't like the drawers either but the good news is you can disable them in Settings > Tools.
- greggarious 4y ago
  > Great comment, I’ll add there’s a MacVim-like GUI wrapper but for Neovim called VimR that i really like. Thanks for pointing this out. One thing I like is being able to command tab in MacOS -- if you have multiple terminal windows it breaks that, so any kind of GUI wrapper, even if it's basically just a glorified replication of the terminal app, is useful from a usability perspective. (To me at least) That's how I originally moved from vim to MacVim -- I wanted terminal for sysadmin stuff, something like Sublime for coding, TexMaker for LaTeX (because it's it's own beast), and so on and so forth.
greggarious 4y ago
Ok my bad, sorry! I use vi (and it's derivitives) since I can get distracted by crap like picking fonts if I use a WYSIWYG editor. I'll give it a test later.
- capableweb 4y ago
  Nitpicking (or maybe educating?) but WYSIWYG is specifically editors that allow you to create things like GUIs by dragging and dropping elements rather than writing code. Most text editors allow you to change the font one way or another, but that doesn't mean they are WYSIWYG editors ("What You See Is What You Get").
  - kens 4y ago
    The standard definition of WYSIWYG is a text editor where what you see on the screen (fonts and all) is what gets printed. Prior to the Bravo text editor on the Xerox Alto, this was not the case.
  - mikestew 4y ago
    To join the (nit)pickin' party, I would argue that MacVim is WYSIWYG in that what comes out of the printer will look just like what's on my screen, minus the editor chrome that MacVim adds. IOW, if :set guifont=Courier_New:h12, then a bunch of code in 12pt. Courier New comes out of my printer.

ARandomerDude 4y ago

Great comment, I’ll add there’s a MacVim-like GUI wrapper but for Neovim called VimR that i really like. https://github.com/qvacua/vimr https://github.com/qvacua/vimr

predmijat 4y ago
There's also Neovide which is written in Rust, which makes it, well, blazingly fast. https://github.com/neovide/neovide https://github.com/neovide/neovide
- halostatue 4y ago
  Neovide is fast, but does not have any macOS-level integration. While it’s nice that it’s not electron like so many other neovim GUIs, it does not work well on macOS.
  - greggarious 4y ago
    Ugh, no offense but I'll skip neovide then -- I hate stuff that does the crap GIMP does where it doesn't blend in with the rest of macOS
halostatue 4y ago
Can't stand it, myself. Of the various Neovim macOS UIs, this is the one that is perhaps closest to MacVim, but the UI choices about having the drawers present all the time and other pieces make it both less reliable and less usable than MacVim itself. That's the main problem with most of the neovim GUIs—they get opinionated about what a Vim GUI should be. First, foremost, and always, it must be vim in a GUI window. Second, it must have native OS keybindings and integration (clipboard, menu, etc.). Finally, it should be able to have possible extensions that work well with existing plug-ins. (I use Fern for my file tree. I don’t need a built-in file tree that is always visible.) They must, at the core, always be vim. This is why I think that Oni2 was a mistake and why it’s one of the few software packages I regret paying. I don’t want vim motion keys with VSCode extensions. I want a Vim GUI.
- ARandomerDude 4y ago
  I don't like the drawers either but the good news is you can disable them in Settings > Tools.
greggarious 4y ago
> Great comment, I’ll add there’s a MacVim-like GUI wrapper but for Neovim called VimR that i really like. Thanks for pointing this out. One thing I like is being able to command tab in MacOS -- if you have multiple terminal windows it breaks that, so any kind of GUI wrapper, even if it's basically just a glorified replication of the terminal app, is useful from a usability perspective. (To me at least) That's how I originally moved from vim to MacVim -- I wanted terminal for sysadmin stuff, something like Sublime for coding, TexMaker for LaTeX (because it's it's own beast), and so on and so forth.

greggarious 4y ago

Ok my bad, sorry! I use vi (and it's derivitives) since I can get distracted by crap like picking fonts if I use a WYSIWYG editor. I'll give it a test later.

capableweb 4y ago
Nitpicking (or maybe educating?) but WYSIWYG is specifically editors that allow you to create things like GUIs by dragging and dropping elements rather than writing code. Most text editors allow you to change the font one way or another, but that doesn't mean they are WYSIWYG editors ("What You See Is What You Get").
- kens 4y ago
  The standard definition of WYSIWYG is a text editor where what you see on the screen (fonts and all) is what gets printed. Prior to the Bravo text editor on the Xerox Alto, this was not the case.
- mikestew 4y ago
  To join the (nit)pickin' party, I would argue that MacVim is WYSIWYG in that what comes out of the printer will look just like what's on my screen, minus the editor chrome that MacVim adds. IOW, if :set guifont=Courier_New:h12, then a bunch of code in 12pt. Courier New comes out of my printer.