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

Support printing to markdown #231

Open
shonfeder opened this issue Mar 15, 2021 · 5 comments
Open

Support printing to markdown #231

shonfeder opened this issue Mar 15, 2021 · 5 comments

Comments

@shonfeder
Copy link
Collaborator

This would allow programmatic construction and transformation of markdown, and (in the special case of a no-op transformation) would serve as a markdown pretty printer.

Request by @jfrolich on at #230 (comment)

@cuihtlauac
Copy link
Contributor

cuihtlauac commented Oct 20, 2022

Not sure if it is already known. ocaml-lsp-server is stuck with 1.3.2:

(omd (and (>= 1.3.2) (< 2.0.0~alpha1)))

It's using Omd.to_markdown in doc_to_md.ml

I believe this is problematic.

@shonfeder
Copy link
Collaborator Author

@cuihtlauac Could you explain what kind of problems you're hitting on 1.3.2?

@cuihtlauac
Copy link
Contributor

cuihtlauac commented Nov 14, 2022

Because ocaml-lsp-server requires omd < 2 it is not possible to have it installed in the same opam switch as packages requiring omd >= 2. Being forced to choose between mutually exclusive dependencies is a problem, I believe.

@shonfeder
Copy link
Collaborator Author

Thanks for explaining. I think this issue is certainly top priority at the moment.

My suggestion for the moment would be to avoid depending on the pre-release versions of 2.0 for any production-grade projects. As noted in the README, we have not yet achieved feature parity with 1.3, and only just recently resolved the lingering bugs causing failures to satisfy the CommonMark spec.

@cuihtlauac
Copy link
Contributor

You're right. Unfortunately, a number of projects have decided not to wait and are relying on 2.0 features, they probably had good reasons too.

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

No branches or pull requests

2 participants