vim-pandoc VS vim-polyglot

With that, the only thing left to do was the make it as convenient as possible to export an MLA-formatted PDF from inside Neovim, so I wrote a custom function using the vim-pandoc plugin as a wrapper to make the command simpler:

See also vim-pandoc, vim-latex, vimura

vim-pandoc is a plugin that uses pandoc external program to convert documents between different formats.

I use vim-pandoc with neovim, it nests # headings as expected. If you install it, check :help vim-pandoc-folding for more info and other options.

From that perspective, raw text might be okay--google drive is mostly treated as a cloud storage system and not really as a place for formatted documents. Markdown is still useful from a vim folding perspective; and generating formatted output (e.g., via pandoc) can be done outside of vim (or perhaps using vim-pandoc or simple script snippets).

What about an alternative markdown syntax plugin? I'm using https://github.com/vim-pandoc/vim-pandoc alongside https://github.com/vim-pandoc/vim-pandoc-syntax (you can also use only the syntax plugin), which does support latex math.

I was trying to use some of Gilles Castel's LaTeX snippets for my own notetaking, which I do on nvim with markdown, using pandoc to convert to pdf. The problem with this is that the tex snippets are designed to be activated only when in LaTeX math, but there's no function to directly check this in the plugin I'm using for pandoc markdown.

I'm trying to cut back on some plugins that I'm not really getting that much out of and clean up my vimrc because it was getting a little bloated. Does anyone know if there is a good way to have a pop-up table of contents in a markdown document for jumping around a document like there is in 'vim-pandoc' (https://github.com/vim-pandoc/vim-pandoc.git) without all the other stuff in that plugin? I suppose I can just use marks but I really liked that one feature. Thanks!

I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

So I did some digging and I found out that vim-polyglot uses a different syntax file than Vim's default for PHP files. When I loaded vim-polyglot's syntax file into my ~/.vim/syntax, I encountered the same issue as you.

Try this: https://github.com/sheerun/vim-polyglot You can install plugin or copy-paste files for desired filetype

I think you mean vim-polyglot? Great plugin. Pre-treesitter it was indespensible.

Usually this is handled inside the :compiler scripts. vim-polyglot is a collection of ftplugins that includes a bunch of :compiler plugins.

Get polyglot installed in your vimfiles/pack//start folder along with whatever 4 Tim Pope plugins you love the most and :CocInstall your LSP(s)

https://github.com/morhetz/gruvbox and https://github.com/sheerun/vim-polyglot are Vim plugins that work in Neovim, but they don't allow you to use treesitter, so if you don't want to use treesitter use them.