-
Notifications
You must be signed in to change notification settings - Fork 76
Any chance this utility published as a library? #18
Comments
@tailhook I can make a lib crate of it, and expose the entry function, but I'd rather not like to think about a useful API or make any promises about compatibility. Honestly, to me that's too much effort for such a small tool. |
If you have a concrete idea where you'd like to use this tool as a library then we can look into it, but I won't publish mdcat as a library just because I could. |
Sorry for being unresponsive. The idea I had in mind is:
However, I'll probably hack some prototype before actually doing any work in this library. |
@tailhook I do not believe that either of these should use mdcat, and personally I'd not like to have to consider these use cases in mdcat. I'd just like to use mdcat to quickly view and navigate a markdown README in my terminal for looking up some stuff, and that's basically the entire scope of this tool. Having to consider other use cases is already too much work for me to be honest. |
Basically I need some markdown to "escape-codes" formatter. So do you recommend just fork this code? |
Yes, perhaps, if it suits your needs I don't mind if you fork it under the terms of its license. But it's in an early stage, and doesn't format all well. Personally, tho, I think better formats exist to provide help. If you'd like to stick to text at least go for man pages which—unlike mdcat—provide some basic cross-referencing—pandoc can turn markdown into man pages—but I believe a good HTML manual works way better than an |
@tailhook Okay, I made Feel free to use, but please understand that I make no guarantees about that interface yet and that I'll change the interface whenever I need it to make my changes to |
No problem. Just make sure to bump major version every time you break the API :) |
@tailhook I'll adhere to semantic versioning, so as long as |
The plan is to use it to provide some markdown formatting in command-line utilities.
What do you think?
The text was updated successfully, but these errors were encountered: