- Markdown keeps opening vimr code#
- Markdown keeps opening vimr free#
- Markdown keeps opening vimr mac#
I don't see any obvious collision (currently # seems to be forbidden anyhow), but feel free to come up with something better. using #!5 (rather than !5) to reference MRs.
Markdown keeps opening vimr code#
i currently don't have a way to use "gitlab-ce#1" without making it either a link to issue#1 (and creating a back-reference there) or marking it as code (which has a distinct look and meaning).Įven better than adding special characters to avoid creating gitlab references, would be have been a generic meta-escape character that starts a gitlab cross-reference. It would be nice, if cross-references could be escaped easily.Į.g. $10 prefixing a number with currency symbol is often used to denote amounts of money. ~5 the tilde ~ is a common abbreviation for approximately #1 using a hash # followed by a number is often used to reference enumerations (in gitlab context this could mean enumerations within a given issue, rather than neighboring issues) It also doesn't really help, that sometimes a reference will expand to a link (if the referenced item exists), and sometimes it stays "as is".Īt the time of writing six (6!) characters ( are overloaded with special meaning (related to gitlab references), making them unusable for other things. This is especially true, for special characters that have a real-world usage that looks similar to the text-representation in GFM.
Unfortunately this also means, that an ever growing number of special characters cannot be used for "normal" text anymore. Of course, I could disable the updating altogether with, but that's just a work-around that removes useful functionality.Gitlab-flavoured markdown keeps adding new shortcuts to create terse, and easy to parse (for humans) textual representation with lots of cross-references. At the suggestion of who found the settings for the scroll synchronization in VSCode, I turned off synchronization from the preview window back into the editor ("": false) this at least removed the jumping from the the editor window making it usable again, but the preview window is still jumping all over the place which is the actual bug.
It seems to be some specific property of the markdown file as two different computers with different screen and window sizes started and stopped behaving exactly the same way with the same files. Of course, a mere few hours afterwards the same problem came back.I am just waiting for the problem to come back. After more than a week trying to fix this, a couple hours after posting this question (and with no changes that I can think of on my part, it seems to have fixed itself).The questionĪny idea what could be triggering it? Update: But nothing recent which surprises me as it is maddening. Online searches show similar behavior reported, and supposedly corrected, several years ago. I am not sure exactly what triggers this behavior, but I suspect it has to do with using any sort of graphic rendering, be it MathJax, Mermaid, or a simple figure. When I am editing a Markdown document with preview alongside it, the text window jumps with the cursor location moving up the window to the point of disappearing at the top. with a minimal set of extensions (I have disabled everything I can), namely:
Markdown keeps opening vimr mac#
I am using the latest version of VSCode (1.45.1) on a mac running OSX 10.15.4. This problem comes and goes, but it's been getting unbearable as times goes on.
0 kommentar(er)
