0

I recently decided to try out nvim, after using vim for a few years. I started following these instructions

I noticed after running these two commands

:call mkdir(stdpath('config'), 'p')
:exe 'edit '.stdpath('config').'/init.vim'    

I can no longer launch a specific app on my machine without it hard crashing (0xc0000409 -- STATUS_STACK_BUFFER_OVERRUN)

If it's any use, this is my nvim.init

set runtimepath^=~/.vim runtimepath+=~/.vim/after
let &packpath = &runtimepath
source ~/vimfiles/vimrc
source ~/vimfiles/gvimrc

I'm wondering if one of these commands is malformed and somehow corrupting my systems registry key or something of the sort? I noticed this happen on two separate machines now, both close in time to when I ran these commands, so I'm fairly certain my nvim configuring has something to do with it.

Has anyone else run into this? Or have any guesses as to what might be happening?

2
  • Welcome to Vi and Vim! I strongly encourage you to also reach out the neovim dev team/community if you have not already done so.
    – D. Ben Knoble
    Aug 16 at 13:18
  • Thank you, I will do that Aug 16 at 15:13
0

Another dev from my company experienced the same crash a few days later. So I don't believe my nvim configuring had anything to do with it.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.