-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vimwiki Markdown Blockquote Syntax issue #915
Comments
So you would like for markdown:
You declare that it is vim default behavior for markdown. So you shoudl have this when remove
|
I apologize @tinmarino ! 99 times out of 100 neovim and vim operate identically, but apparently this is one instance where they do not. Neovim does this by default. Not Vim. Wow, I had no idea Neovim had superior syntax behavior. Unfortunately I do not know vimscript, in the least. I can link to the files that I think are a jumping off point, but I really don't know. https://github.com/neovim/neovim/blob/master/runtime/syntax/markdown.vim There are no other files specifically on markdown. I imagine that there's something that defines the > precursor to follow some kind of folding larger folding mechanism but it will take me a good long time to figure out how that works, not knowing the codebase or the language. Apologies for the confusion! |
I have a related issue (let me know if I should open up a separate issue for this?) - when formatting blockquotes (
Interestingly enough, it looks like the markdown files in vim are more recent than the ones in neovim? https://github.com/vim/vim/blob/master/runtime/syntax/markdown.vim |
…sue vimwiki#915) Wrap: autoadd a new `> ` on new create lines with `setlocal comments+=n:>` Join: autoremove the inter `> ` with `setlocal formatoptions+=j`
Thank you very much for the details, both @kejadlen and @malan88. They were very helpfull : you did 90% of the analisys. 1 gqqThe solution for
Which should be copied in ftplugin/vimwiki 2 JJust add FixedSee the PR referencing this issue (the last non closed one) |
Note: |
…sue vimwiki#915) Wrap: autoadd a new `> ` on new create lines with `setlocal comments+=n:>` Join: autoremove the inter `> ` with `setlocal formatoptions+=j`
…sue vimwiki#915) Wrap: autoadd a new `> ` on new create lines with `setlocal comments+=n:>` Join: autoremove the inter `> ` with `setlocal formatoptions+=j`
Also next time, if you do not want to wait for a fix, add this to
|
…sue vimwiki#915) Wrap: autoadd a new `> ` on new create lines with `setlocal comments+=n:>` Join: autoremove the inter `> ` with `setlocal formatoptions+=j`
…sue vimwiki#915) Wrap: autoadd a new `> ` on new create lines with `setlocal comments+=n:>` Join: autoremove the inter `> ` with `setlocal formatoptions+=j`
Thanks for the fix! I've switched to the |
…sue vimwiki#915) Wrap: autoadd a new `> ` on new create lines with `setlocal comments+=n:>` Join: autoremove the inter `> ` with `setlocal formatoptions+=j`
Has this been merged? I don't see any PR for it. |
Hi @newptcai, I think I pushed directly to |
…sue vimwiki#915) Wrap: autoadd a new `> ` on new create lines with `setlocal comments+=n:>` Join: autoremove the inter `> ` with `setlocal formatoptions+=j`
Prior to submitting a new issue make sure to complete these steps:
dev
branch and confirm the issue is present there as well.The
dev
branch contains fixes that may not have been merged tomaster
yet..vimrc
:VimwikiShowVersion
.Using markdown
Output of
:VimwikiShowVersion
: Stable version: 2.5Hi,
There's a functionality with Vim's native markdown syntax involving blockquotes whereby a blockquote of the form
can be joined and the result will be
Continuing to type and hard wrapping to the next line will automatically insert a new > for continuation, just like a comment in, say, Python.
Vimwiki does not abide by this syntax rule. To join the first line to the second (with a
J
command) results in:To be fair, I'm not sure how vimwiki interprets markdown blockquote syntax. It seems like they continue to use the 4 spaces for quotes syntax, as with vimwiki syntax, which I'd argue is specifically not markdown syntax.
I added
let g:vimwiki_global_ext = 0
to my vimrc because I rely on markdown quotes in a variety of places, even outside vimwiki, and the vimwiki markdown syntax is demonstrably worse than the standard vimwiki syntax for this very reason. I would love to be able to use vimwiki's linking outside of vimwiki, and it's syntax support, but unless there is a way to fix this blockquote issue I cannot.Thank you,
M.
The text was updated successfully, but these errors were encountered: