Denis Laxalde
Denis Laxalde
One thing I'm not sure we can easily replace is the overlay confirmation dialog when the user requests process cancel or kill. It's possible to emit a confirmation message, similar...
> The fact that the size of the columns is potentially changing at each > refresh is a little distracting. > What do you think about this ? I agree....
> * add a "--unprivileged-user" / "--no-superuser" option, and use it to disable parts of the queries > that require superuser or additional permissions If we go with requiring superuser,...
> Ok, I was slightly worried we would end up with `--azure`, `--google` etc.. Ah, yes. Might be a good reason to drop the option then.
> We could also make a `--no-temp-size` since it's the only thing requiring special rights right now. But as features add in we could end up with a slew of...
About content width and smaller screens, that's true. But we're already quite bad as the process table has a fixed (and large) width. That should be improved overall, but I'm...
I like the idea of cycling through a subset of columns.
I have started working on this topic. Here are the steps I imagine: 1. port code from `psycopg/` directory to use anyio instead of asyncio, almost done in #146 2....
The approach taken in #146 is rather to introduce anyio support as a way to allow usage of trio, this does not replace the asyncio implementation (though it's obviously possible...
> What is the advantage of using anyio? The advantage is that we have a single implementation on our side that's independent of the underlying async library (asyncio or trio...