Skip to content
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

Mention of e.g. C++ in previous normal text breaks the Plugins default behaviour #86

Open
francwalter opened this issue Dec 12, 2023 · 1 comment

Comments

@francwalter
Copy link

francwalter commented Dec 12, 2023

Hallo

after a while of search I noticed that when I have some ++ in normal text, which is not so uncommon, e.g. C++, the next folded plugin use breaks the formatting of the document.

Here some example code:

Is C++ better than C# or is Visual Studio Code better? Or Visual Basic 6.0 in the end? blablabla etc.



++++ Click to unfold... | 

Unfolded area

++++

This makes the text since the first ++ (from C++) all clickable and not only the Click to unfold, here a little screenshot:

grafik

I dont know if this is a bug, but it took me a while to find it. First I thought it is related to my very long article, but its the ++ in the text obviously.

Shouldnt the ++ in between some normal text be ignored? The plugin needs four times the + and not only two and at the beginning of the line. In the middle of a line I think the + characters should be ignored, shouldnthey?
Is it fixable? Or by design?

Thanks, frank
Release 2023-04-04a "Jack Jackrum" on Ubuntu 22.04

@spd-spd
Copy link

spd-spd commented Apr 10, 2024

I'm also having this problem. Mention of C++ is starting and ending folded sections, even though the 2 + characters are on separate lines. My understanding of the inline version is that it should only activate if there is an open and a close pair of ++ on the same line, My fix suggestion would be to make the multi-line inline option use a longer character activation sequence (which is hopefully rarer in normal text), something like ++-- and then --++ at the end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants