Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

How do i prevent markdown-preview from breaking autocompletion (markdown-plus)?#6743

Answeredbydpetka2001
j-steinbach asked this question inQ&A
Discussion options

E: The issue came from markdown-plus, not blink.cmp as I initially assumed. Updated the discussion title to reflect this.

Our AI overlords told me that this is a known problem,
but I didn't find anything useful in the markdown-preview, blink.nvim or LazyVim docs.
(Well, maybe my ability to search for help has regressed since I started vibe-code everything.)

Either way,
here is the problem:

I haverender-markdown.nvim andblink.cmp installed via the LazyExtras.

When I do<spc>cp to do MarkdownPreview,
and then return to the originating buffer,
all my autocompletions are broken.

Switching to another buffer where I didn't run MarkdownPreview previously everything works fine.
If I run MarkdownPreview in there,
completions also stop working.

I tried all the MarkdownPreview commands (Toggle, Stop, ...) to no avail.

My list of plugins.
99% installed via LazyVim Extras,
with minimal (none) configuration.

auto-save.nvimhttps://github.com/okuuva/auto-save.nvimblink.cmphttps://github.com/saghen/blink.cmpbufferline.nvimhttps://github.com/akinsho/bufferline.nvimcatppuccinhttps://github.com/catppuccin/nvimconform.nvimhttps://github.com/stevearc/conform.nvimdial.nvimhttps://github.com/monaqa/dial.nvimflash.nvimhttps://github.com/folke/flash.nvimfriendly-snippetshttps://github.com/rafamadriz/friendly-snippetsgitsigns.nvimhttps://github.com/lewis6991/gitsigns.nvimgrug-far.nvimhttps://github.com/MagicDuck/grug-far.nvimlazydev.nvimhttps://github.com/folke/lazydev.nvimlazy.nvimhttps://github.com/folke/lazy.nvimLazyVimhttps://github.com/LazyVim/LazyVimlualine.nvimhttps://github.com/nvim-lualine/lualine.nvimmarkdown-plus.nvimhttps://github.com/yousefhadder/markdown-plus.nvimmarkdown-preview.nvimhttps://github.com/iamcco/markdown-preview.nvimmason-lspconfig.nvimhttps://github.com/mason-org/mason-lspconfig.nvimmason.nvimhttps://github.com/mason-org/mason.nvimmini.aihttps://github.com/nvim-mini/mini.aimini.hipatternshttps://github.com/nvim-mini/mini.hipatternsmini.iconshttps://github.com/nvim-mini/mini.iconsmini.pairshttps://github.com/nvim-mini/mini.pairsnoice.nvimhttps://github.com/folke/noice.nvimnui.nvimhttps://github.com/MunifTanjim/nui.nvimnvim-linthttps://github.com/mfussenegger/nvim-lintnvim-lspconfighttps://github.com/neovim/nvim-lspconfignvim-treesitterhttps://github.com/nvim-treesitter/nvim-treesitternvim-treesitter-textobjectshttps://github.com/nvim-treesitter/nvim-treesitter-textobjectsnvim-ts-autotaghttps://github.com/windwp/nvim-ts-autotagpersistence.nvimhttps://github.com/folke/persistence.nvimplenary.nvimhttps://github.com/nvim-lua/plenary.nvimrender-markdown.nvimhttps://github.com/MeanderingProgrammer/render-markdown.nvimsnacks.nvimhttps://github.com/folke/snacks.nvimtodo-comments.nvimhttps://github.com/folke/todo-comments.nvimtokyonight.nvimhttps://github.com/folke/tokyonight.nvimtrouble.nvimhttps://github.com/folke/trouble.nvimts-comments.nvimhttps://github.com/folke/ts-comments.nvimvenv-selector.nvimhttps://github.com/linux-cultist/venv-selector.nvimwhich-key.nvimhttps://github.com/folke/which-key.nvimyanky.nvimhttps://github.com/gbprod/yanky.nvim
You must be logged in to vote

You start by trying with a minimal LazyVim repro. Save the following

vim.env.LAZY_STDPATH=".repro"load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()require("lazy.minit").repro({spec= {    {"LazyVim/LazyVim",import="lazyvim.plugins"},    {import="lazyvim.plugins.extras.lang.markdown"},-- add any other plugins here  },})

in a file calledrepro.lua and then open Neovim withnvim -u repro.lua some_markdown.md. Trigger markdown-preview with<leader>cp and see what you observe.

From my testing I could not repro. If you also don't observe that behavior with the mentionedrepro.lua, then most probably it's something wit…

Replies: 1 comment 3 replies

Comment options

You start by trying with a minimal LazyVim repro. Save the following

vim.env.LAZY_STDPATH=".repro"load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()require("lazy.minit").repro({spec= {    {"LazyVim/LazyVim",import="lazyvim.plugins"},    {import="lazyvim.plugins.extras.lang.markdown"},-- add any other plugins here  },})

in a file calledrepro.lua and then open Neovim withnvim -u repro.lua some_markdown.md. Trigger markdown-preview with<leader>cp and see what you observe.

From my testing I could not repro. If you also don't observe that behavior with the mentionedrepro.lua, then most probably it's something with your personal configuration and only you can debug it to find out what's wrong.

You must be logged in to vote
3 replies
@dpetka2001
Comment options

Here's also a screencast with the aboverepro.lua and what I observe in the Snacks README.md with autocompletion before and after I trigger markdown-preview with<leader>cp.

Screencast_20251103_224759.webm
@j-steinbach
Comment options

Yes, indeed, the issue came fromyousefhadder/markdown-plus.nvim, which is not included by Lazy.

Lessons learned

  • don't trust Ai, despite how much it assures you that plugin XYZ is the root cause
  • disable plugins one-by-one to find the root cause

I think I will just remove the markdown-preview instead of fixing it though, as I rarely use it.render-markdown better fits my use-case.

Thank you very much for your help!

@j-steinbach
Comment options

E: Filed a bug report here:YousefHadder/markdown-plus.nvim#101

Answer selected byj-steinbach
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
Q&A
Labels
None yet
2 participants
@j-steinbach@dpetka2001
[8]ページ先頭
©2009-2025 Movatter.jp