Open augustebaum opened 3 years ago
Yeah seem to have the same issue here, cant run it with init.lua , using Fedora Silverblue:
health#mkdp#check
========================================================================
- INFO: Platform: linux
- INFO: Nvim Version: NVIM v0.5.0
- INFO: Pre build: /var/home/cerqueira/.local/share/nvim/site/pack/paqs/opt/markdownPreview/app/bin/markdown-preview-linux
- INFO: Pre build version: pkg/prelude/bootstrap.js:1254
- OK: Using pre build
I am using paq.nvim on my init.lua
require "paq" {
"savq/paq-nvim"; -- Let Paq manage itself
{"iamcco/markdown-preview.nvim", opt=true ,run=vim.fn["mkdp#util#install()"] ,as="markdownPreview"} ; -- Markdown Preview
}
vim.cmd([[
augroup markdown!
autocmd!
au FileType markdown packadd! markdownPreview
au FileType markdown setlocal spell spelllang=pt_pt,en_us
au FileType markdown inoremap <C-l> <c-g>u<Esc>[s1z=`]a<c-g>u
au FileType markdown nmap <F5> <Plug>MarkdownPreviewToggle
au FileType markdown set conceallevel=2
augroup END
]])
@augustebaum @motorto ran into this issue today. Solved it by running this for the run hook:
require "paq" {
'savq/paq-nvim';
{ 'iamcco/markdown-preview.nvim', run = function() vim.fn['mkdp#util#install']() end };
}
Any updates on this? I tried @logan-connolly solution, but didn't work..
Describe the bug When I use
init.vim
the preview starts as normal, and when I useinit.lua
nothing starts, with no errors.To Reproduce
Install
vim-plug
andpaq.nvim
(sorry, apparently one can't usevim-plug
withinit.lua
so I had to change when I rewrote it).Take
and
and install the plugin (with
:PlugInstall
for the first and:PaqInstall
for the second).Open some markdown file using
nvim -u init.vim file.md
. Run:MarkdownPreview
. Works as expected (server starts atlocalhost
, browser opens it).Open the markdown file using
nvim -u init.lua file.md
. Run:MarkdownPreview
. Nothing happens (and no errors). In particular, the server doesn't seem to have started (when I use the address I have when it works, I get "not found").Expected behavior Everything works exactly the same for the two setups.
Desktop:
Log:
checkhealth
gives:Otherwise the plugin has been working great, thanks for all your hard work!