I appreciate your comment, but I made mermaid-ascii OSS under MIT license so that everybody can use it in whatever fashion they like, be that in another OSS project or in your company. I’m just happy to contribute back to the ecosystem, and I’m excited seeing my projects being used by others.

Nothing but good vibes to these guys. Let’s all strive to keep making cool things, and leave things a little better than how you found it ;)

I'm going to take that as an implicit (and generous) request to put the submitted URL back at the top, so I've done this, and included the two links to your work in the toptext. Seems like a fair balance. Thank you!

Thanks for the credits!

Added it to https://udiagram.com

Yes, over the course of time I want to increase the coverage of the Mermaid syntax.

PS: it's open source so feel free to help out ;) https://github.com/AlexanderGrooff/mermaid-ascii

The example you post works just fine ;)

On a serious note, yes not all syntax noted in the Mermaid docs work yet. I'm planning on adding more coverage of the Mermaid syntax over time. For now the basics work and (hopefully) shows its potential.

Yeah, first try I copy pasted the pie charts example wondering how it would render in ascii and was noooo

Thanks for the recommendation. I've added the "+" corners in v0.5.1.

Thanks, that's a good suggestion. I'm also noticing that's not working as intended.

Fixed in 0.5.0. Give it a try!

Thanks for the kind words!

Thanks for the feedback! I agree that the web UI can be improved (quite) a bit, most of my efforts went into the actual generation of the diagrams. I'll have a look at prettifying it.

I've found that AppArmor started to block Firefox:

audit: type=1400 audit(1642063521.864:246): apparmor="DENIED" operation="ptrace" profile="snap.firefox.firefox" pid=9868 comm="Shutdow~minator" requested_mask="trace" denied_mask="trace" peer="snap.firefox.firefox"

I really don't like it, but turning off Apparmor worked for me. Not sure what caused AppArmor to start complaining all of a sudden.

Your policy is blocking ptrace from processes that don't seem like they should need ptrace (very few processes need ptrace). So why would Firefox need ptrace? Some cursory googling suggests that ptrace is used for plugins and by the crash reporter.

There are apparmor profiles for Firefox, e.g. this one: https://github.com/nibags/apparmor-profiles/blob/master/appa... Maybe you could add it to your system and see if that fixes things.

This seems to fix it, even though there was already a default apparmor config for Firefox (which looked _very_ familiar).

Thanks!

That smells like the Shutdown Hang Terminator triggering a crash report.