Christian Muehlhaeuser

> Looking deeper at the code, it feels like it must be done at the parser level, not renderer level, @muesli what do you think? Yeah, I don't think we...

This has been fixed upstream and a `NO_COLOR` environment variable will be respected by `termenv`, which then strips all styling & color output. `notty`'s broken indentation will have to be...

Not at the moment, but it's something we'll work on.

We actually do have some fuzz testing in https://github.com/charmbracelet/glamour/tree/master/testdata/fuzz. I think we should migrate to Go's own fuzzer however: https://go.dev/security/fuzz/ I'd be curious to hear about the bugs you've found...

We pad the content to ensure the background color gets rendered.

Sorry about that, but it's a slightly more involved change in the renderer. We're working on a bit of a refactor to improve handling nested elements.

@Jarmos-san Happy to include this in glamour. We've designed the style system to be flexible and were hoping people would come up with their own styles!

> Would you like to receive a PR with the stylesheet? I don't mind sharing it for `glamour` tbh. Yes, please 😊

> Looks like `rivo/uniseg` update would require Go 1.18, so I've updated accordingly. You're right, already noticed that in other projects as well. Will try this out asap, thanks for...

Thanks for confirming, @IGLOU-EU. See comment on #245.