-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Prettier gaurds move #62
Comments
I’d like ideas on how to debug this (via logs or something) |
Pushing to top, I now have more insight on the repro. I tried debugging but this vimscript-fu is beyond my abilities :) A: First, you need to also have:
B: Then you need to have a liquid front matter. Now load a file that looks like this: ---
t:1
---
A
<!-- vim-markdown-toc GFM -->
- [Hello](#hello)
<!-- vim-markdown-toc -->
B
# Hello
Put your cursor on the line with text A, then ---
t:1
---
A
B
<!-- vim-markdown-toc GFM -->
- [Hello](#hello)
<!-- vim-markdown-toc -->
# Hello
|
Poke @mzlogin |
@idvorkin I'm sorry but I can't reproduce your phenomenon. Would you please provide more details, like your complete vim settings. |
Thank you for the help! Simplified vimrc
|
I also observed a 100% repro if I load the file from disk and then do the save before making any other changes. @mzlogin |
If I remove this line, everything will work well. But I still don't know why. |
Thx. If it's helpful, a theory I had (though didn't test) was folding is interfering with the view computations I wondered if a different approach would help. Like instead of erase the toc guards, leave the guards, delete toc and re-insert toc. |
I’m not sure what is going on or the exact repro. The symptom is sometimes the prettier gaurds that were around my toc marks move. A “phychic debugging” is the toc is written a few lines below it’s original line. I’ve tried a few things to isolate this, but haven’t found a consistent repro. I think it’s more likely if I hit save above the TOC, as opposed to below it, but sometimes I get a repro below as well. See video.
The text was updated successfully, but these errors were encountered: