Philippe Vaucher

Just a heads-up: I'm working on the async implementation and I found aio which produce very clean code (compare https://github.com/Silex/docker.el/blob/aio/docker-network.el#L90-L94 vs https://github.com/Silex/docker.el/blob/async/docker-network.el#L115-L128 (the comparison is not completely fair but you...

Well, podman is not supported (see #110). If you think it's feasible to support it, please help provide a path toward that. Supporting old dockers is also not a priority...

That said, removing `dangling=true` can be disabled partially by using setting `docker-show-status` to nil, but then we need some new variable like `docker-no-pretty-listings` which would use `docker-container-entries` instead of `docker-container-entries-propertized`,...

Hello, Yes sure, would that work a bit like projectile? Or more like a tabulated list of previously used docker-compose projets with columns summarizing the running/stopped/etc containers? I'm a bit...

Ah, you meant an issue _here_ :laughing: I thought you meant an issue on transient. I'll create one.

Ah interesting. My wild guess is that TRAMP is not reentrant or whatever it is called and does not support multiple tramp connections at the same time. Can you confirm...

I think there's the same behavior if you select multiple running containers and open a shell inside them.

One easy fix would be to make things sequential when TRAMP is used but I'm not sure how.

I don't see a simple way to force tramp to become sequential so I'll just close this :shrug: Would it make sense to disable transient statuses when over tramp maybe?...

Duplicate of #137