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

> 32 nested balanced parens in a link is bananas #48

Merged
merged 1 commit into from
Jul 12, 2017

Conversation

kivikakk
Copy link

@vmg
Copy link

vmg commented Jul 12, 2017

:seemsgood: :seemsgood:

What does the output look like when you hit the threshold? That's a good thing to know and document. Does it just show the plain Markdown syntax?

@kivikakk
Copy link
Author

Yep — it's just treated as broken syntax, same as if the parens weren't nested correctly at all. Any idea where this is best documented?

@kivikakk kivikakk mentioned this pull request Jul 12, 2017
@kivikakk kivikakk merged commit 298d9d2 into master Jul 12, 2017
@kivikakk kivikakk deleted the kivikakk/limit-nested-parens branch July 12, 2017 08:43
@vmg
Copy link

vmg commented Jul 12, 2017

I was leaning towards "in the spec", but again I believe this should be a corner case that should never be hit during normal Markdown usage, so I'm not sure there's value on documenting it explicitly.

Let's wait and see who complains. :)

@Alhadis Alhadis mentioned this pull request Jul 16, 2017
@Alhadis
Copy link

Alhadis commented Jul 16, 2017

MY LISP CODE.

WHAT HAVE YOU DONE?!

(I kid, I kid))))))))))))))))))))))))))))))))))))))
)))))))))))))))))))))))))))))))))))))))))))))))))))))]]]]]]]]]]]]]]]]]]]]]]]]
((((((((((((((((((((((((((O)))))))))))))))))))))))))))))))))))))

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

Successfully merging this pull request may close these issues.

3 participants