2/19/2023 0 Comments Macvim hangs![]() My custom vimrc is here: Josephs-Mini.vim josephreddington$ defaults read | grep 'MM\|SU'. A good starting point for Vim itself is the Vim tutor which you can probably find by typing 'vimtutor' (without the quotes) in a terminal. I would therefore recommend that you start by finding your way around the Vim documentation and Vim itself. ![]() and I get the same error with /Applications/MacVim.app/Contents/bin/mvim -u NONE -U NONE. Documentation of Vim plugins (rightfully) assumes that you know your way around Vim itself. This appears to be part of a few linked bugs on MacVim, I have quite a lot of trouble with the display not refreshing if I've changed the zoom level while the app is already full-screen and that's quite frustrating. Porting to Neovim means redoing all those work and maintaining a cross-compatible code base. It's a pretty significant amount of work to port MacVim to Neovim, in particular because there are a lot of modifications to Vim source code to allow for MacVim to happen. and there is a 40 second video of the problem here:, which, thankfully, shows the same black border I see. This probably will not happen in foreseeable future. If you configure based on FileType, try opening those files to see if it's a type-specific issue that you're running into. (except, bizarrely, it isn't, because I see a black boarder, the mac screenshot shows a light gray one, and the image uploaded to SE mysteriously makes it white, which suggests there's something wrong with me) If your version of vim has been compiled with the startuptime flag, you can record the startup time for plugins and your vimrc with: vim file.txt -startuptime startup.log. ![]() If I do that, then I get a strange black boarder around the added bit of the window and the whole thing freezes. If I open Macvim, everything works fine, unless I zoom in (using Cmd " "). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |