iamcco/markdown-preview.nvim

Doesn't start with init.lua

Open

#356 opened on Jul 7, 2021

View on GitHub
 (3 comments) (7 reactions) (0 assignees)JavaScript (5,538 stars) (246 forks)batch import
help wanted

Description

Describe the bug When I use init.vim the preview starts as normal, and when I use init.lua nothing starts, with no errors.

To Reproduce

  1. Install vim-plug and paq.nvim (sorry, apparently one can't use vim-plug with init.lua so I had to change when I rewrote it).

  2. Take

" init.vim
set nocp
filetype plugin on
let g:NVIM_PLUGINS_DIR = stdpath('config') . '/plugged'
call plug#begin(NVIM_PLUGINS_DIR)
Plug 'iamcco/markdown-preview.nvim', { 'do': 'cd app && yarn install' }
call plug#end()

and

-- init.lua
vim.o.cp = false
vim.cmd("filetype plugin on")
require "paq" {
{"iamcco/markdown-preview.nvim", as="markdown-preview", run="cd app && yarn install" };
}

and install the plugin (with :PlugInstall for the first and :PaqInstall for the second).

  1. Open some markdown file using nvim -u init.vim file.md. Run :MarkdownPreview. Works as expected (server starts at localhost, browser opens it).
  2. 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:

  • OS: Mac OS X 10.14.6

Log:

checkhealth gives:

health#mkdp#check
========================================================================
  - INFO: Platform: macos
  - INFO: Nvim Version: NVIM v0.6.0-dev+9-g490615612
  - INFO: Node version: v16.4.2

  - INFO: Script: std('data')/site/pack/paqs/start/markdown-preview/app/server.js
  - INFO: Script exists: 1
  - OK: Using node

Otherwise the plugin has been working great, thanks for all your hard work!

Contributor guide

Tech stack
javascriptnodejs
Domain
tooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Neovim setupBasic Lua syntaxNode.js installed
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the difference in behavior when using init.lua vs init.vim. Focus on how the plugin's autoload or startup code initializes. Check the plugin's main entry point (e.g., autoload/mkdp.vim or lua/ directory) for any vimscript specific functions that may not be called when using Lua based init. Review the issue comments for any hints from the maintainer or other users. A possible fix is to ensure the plugin's initialization works identically under both configurations.