Balázs Cene

Hey again! I'm taking a bit of time off from all things programming related for personal reasons, but once I'm back I'm planning on focusing on the new documentation, which...

Since documentation is taking a lot longer than intended, here is what I would do in your case: You already have `self._container` defined, so you can manipulate its widgets as...

I've also seen this happen, but not sure why. Theoretically, setting an alternate buffer should mean that no scrollback is preserved after exit, but iTerm doesn't seem to respect this...

@SomwareHR yup, at the moment the library's windows support is more "this works? cool" than "this _has to_ work". I elaborated on this in some previous issues, but the basic...

@Tired-Fox > @bczsalba Let me know if this is something you want to integrate into the library The current screen clear method is quite simple (just writes `\x1b[2J` to stdout...

Hey there! The `exit` part of the docs is completely valid, that method was removed with `5.0.0` as it was no longer necessary (`stop` did the same thing already). I...

Yup, no idea where `PTG_NAMESPACE` came from. Thank you for letting me know about the issue, I'll close this thread when the docs have been "modernized".

I very much agree with all the points made above! The API docs are pretty much 100% up to date, as they are generated straight from the source, but the...

So I've added both a simple boilerplate application: And a simple (and very yellow, for some reason) implementation of said boilerplate app: To the repo. Thank you for the suggestions!

> BTW the provided code in `boilerplate.py` still calls exit(), instead of stop(), resulting in the error originally reported in this thread. Old habits die hard, or whatever they say...