-
-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After I moved My setup to lazy markdown didnt work #647
Comments
Might be part of the problem, this file seems highly sus: https://github.com/iamcco/markdown-preview.nvim/blob/master/app/install.cmd Could you try to rename that file in your local copy and also change this line to say |
Well, the thing is it did work before when I had some files in different folders. Now that I fully moved to lazy from my old packer setup it is not working anymore. I will try it out. |
The first line of the file invokes powershell with the rest of the contents of the file and exits. |
I still have the problem. is there any prerequisite for windows powershell? |
Seem to be having the same issue. The install fails as i use nvim on powershell (powershell 7.4.0 to be exact). To bypass this i can navigate to the lazy install directory and run the markdown-preview/install.cmd using command prompt, following which the plugin works as intended. I would like to avoid doing this as i tend to run the same config on different machines and this seems to be a pretty awkward workaround. |
Did some testing. So I believe what actually happened is that since we set the default shell to be powershell, we have to specify the command like so |
I encountered this same issue on Arch Linux. I hadn't used this plugin in a while, and realised it wasn't working a week or two ago (running I manually ran I don't know what broke this. |
yea, I got it working the same way, will investigate further when I get some time. |
Describe the bug
After switching to lazy it was not working. I have tried reinstalling the plugin but it gets stuck in the terminal part. I also tried just waiting for some hours, but after waiting for 2 hours nothing happened.
To Reproduce
-- Code --
Steps to reproduce the behavior:
Expected behavior
Be able to finish setup and work properly
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: