iamcco/markdown-preview.nvim

Inserting a code block delays real-time previews

Open

#187 opened on May 7, 2020

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

Description

Hello!! Markdown-preview works pretty well in my environment. But adding a code block delays the real-time preview. Everything else works fine, but when I move the cursor in the code, the display being moved to Chrome is delayed. Do you need any settings?

[issue]

code block

[Environment] Ubuntu 20

.config │ nvim ├── colors │   └── material-monokai.vim ├── dein.toml ├── dein_lazy.toml ├── functions.rc.vim ├── init.vim ├── keymap.rc.vim ├── options.rc.vim ├── plugins └── snippets ├── c.snip └── markdown.snip

dein.toml . . . [[plugins]] repo = 'iamcco/markdown-preview.nvim'
on_ft = ['markdown', 'pandoc.mardown', 'rmd'] build = 'sh -c "cd app & yarn install"' hook_add = ''' let g:mkdp_refresh_slow = 1 let g:mkdp_command_for_global = 1 let g:mkdp_open_to_the_world = 1 let g:mkdp_echo_preview_url = 1 '''

Contributor guide

Tech stack
javascriptnodejs
Domain
performancefrontend
Issue type
performance
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.
needs investigation
Prerequisites
Neovim basicsJavaScript debugging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the performance delay when inserting code blocks in real time preview. Check the rendering pipeline in the plugin's source code, likely in app/ directory. Look for any expensive operations triggered by code block syntax highlighting or preview refresh. Review existing comments or configuration options like g:mkdp refresh slow that might affect performance. Profile the preview to identify bottlenecks.