this post was submitted on 19 Mar 2025
19 points (100.0% liked)

Programming

19246 readers
32 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 2 years ago
MODERATORS
 

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, cp or mv
  • We don't want to inhibit when running stuff like htop, less, watch
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 4 points 1 week ago

It can't be the terminal that decides what inhibits and what doesn't. It must be the user or programs themselves.

How would implementing it in the terminal rather than shell look like? As a user choice? I don't see how that's reasonably possible.

Reading the other comments it seems like there's already inhibit commands.

If the shell does not provide a command or alias, or they can't because the inhibit API is system dependent, it's on the user to define. The user could define a fg alias or command, fg for foreground, which executes the command with inhibition.