OVIWrite icon indicating copy to clipboard operation
OVIWrite copied to clipboard

Missing plugins

Open aidenconri opened this issue 1 year ago • 2 comments

So, I am totally new to vim and nvim. I installed lazy vim without issue, but when I tried to install OVIWrite--things didn't go as planned. More than half of the plug-ins do not work / won't load, and I don't know what to do in order to fix them.

Screenshot 2024-03-01 at 10 51 03 PM

I've tried loading the screen you see above to clean, update, install, and restore them but no action seems to be helping and when I load up terminal, it tells me that something related to the Mason plugins cannot be found or something... honestly, the errors fly away too quickly for me to read them. If it's not "mason" it might be "markdown," but I'm pretty sure it's mason. [Edit: managed to get a screen shot of it happening.]

Screenshot 2024-03-01 at 11 05 37 PM

Oh, and I can't seem to figure out how to quit--and, no, that's not me just meme-ing--Whenever I had lazy vim running, I could type a bunch of mumbo jumbo, delete it to a blank page and just do :qa and get out. Here, if I type a single stroke I keep getting errors about how nothing has been saved or created and it won't let me leave the environment. I have to type :wqa! or :qa! in order to leave. Even then sometimes, I have to just close out terminal and abandon everything. Is there some kind of workflow I have to do in order to make this work properly? Or am I just missing something?

Also, I can't seem to activate neotree anymore by typing ctrl + n--though that may or may not be related.

Any suggestions would be helpful.

aidenconri avatar Mar 02 '24 03:03 aidenconri

Hello

Firstly, I am sorry I've taken so long to reply to this. I've been busy with my writing and didn't have too much to look into this.

To solve this, could you please provide your system details please, specifically what OS are you running on?

MiragianCycle avatar Apr 04 '24 11:04 MiragianCycle

Hi all, On my Linux Mint system, the errors in the screenshot above were solved by installing Node Version Manager (nvm) and using it to install node.js. Good luck!

sbishop333 avatar Oct 01 '24 21:10 sbishop333