A person, on the Gnome Issue, suggested that terminals inhibit sleep when there is stuff running in them.
Continuing from that discussion, I am trying to understand, at which point it would be desirable to implement said inhibition - terminal emulator, the shell or the program itself
Additionally:
- We want to inhibit when running stuff like
pacman,wget,cpormv - We don’t want to inhibit when running stuff like
htop,less,watch



I use
gnome-session-inhibitquite a bit, but it’s hard to imagine a good way to automate it.Sometimes I inhibit
idleto keep something on screen, and sometimes I just inhibitsuspendso something can complete.It probably doesn’t make sense for the terminal to have anything more than a protocol to control it. The only real benefit to that would be in remote sessions, and it’s not really clear how it should work when multiple machines are involved.