Ofek Lev
Ofek Lev
> * Better coupling of the `click.HelpFormatter` methods and rich-click's implementation, mostly revolving around the buffer. Handled by https://github.com/ewels/rich-click/pull/231
I face a similar situation to this and https://github.com/ewels/rich-click/issues/19. I'm trying to auto generate HTML documentation. What would be a way to get HTML output without printing to stdout?
The solution currently appears to be that an application must manage its own custom subclass of `RichContext` so that you can set the value of [this](https://github.com/ewels/rich-click/blob/v1.8.8/src/rich_click/rich_context.py#L23) `export_console_as` class attribute to...
https://github.com/ewels/rich-click/pull/230
Thanks! I think the missing context is that documentation generators such as the one I maintain and the one described by the opening post of this issue cannot use the...
I think the downside of what you're saying is the impact on users. In my application I just so happen to have complex requirements where I already had a custom...
> If that's the case, I'm not even 100% sure that `export_console_as` is the right approach for your users. [...] To be honest, I am reluctant to expand the API...
Talking this out is very helpful so I appreciate your patience! Upon further thinking, I actually do not need HTML and I was just lucky in my tests that the...
1. Shouldn't be a problem if there are ANSI codes! Do you know if Rich has a utility to strip them, or if you recommend some alternative mechanism to do...
Can you show examples of configuration that you have tried?