I'm not quite sure where to put this request, but since I believe this behavior is built into the core app, I'll put it here. Whenever I use the widgets plugin to launch what is supposed to be a backup process, I always end up with a [Process completed - press Enter] message popping up immediately after. This window doesn't offer any new information unless the process failed and is printing error text. Therefore, it goes against the general Unix principle of minimal information output and user interaction.

Example use cases: A lot of my widget shortcut scripts are meant to run very quickly, spawn whatever forking processes they need, and then exit with no STDOUT. For example, I have one called start-sshd that consists simply of:

termux-wake-lock
sshd

The window popup serves absolutely no function in this case or in any of my other daemon management scripts (which are meant to handle things like sshd and nginx).

At the same time, of course, it is very useful to have the option to display text output, e.g. for using termux-battery-status as a one-click battery status checking utility.

So, the way I see it, there are several ways to engineer a relatively simple solution while keeping the best of both worlds:

1. Have a user-configurable option to skip the popup on a special case basis. (Con: adds configuration complexity.)
2. Have the popup skipped if the program doesn't output anything. (Con: does not alert user to exit code, but I don't believe the current system does either.)
3. Have the popup skipped based on if the exit code is zero. (Con: does not allow scripts like termux-battery-status that are meant to display stuff to work, without a wrapper that adds a spurious exit 1 or somesuch to the end as a workaround)

In general, I think the window popup should be replaced with a small fading message to alert the user that it exited successfully -- so no matter which option we use, the user knows their script ran. This fading message could even specify the exit code, which would be a nice hint as to what's going on without being obtrusive.

I'm curious to know which solution people think is best, and if anyone has any better ideas! Also, sorry if I put this in the wrong place. I'm really not sure where to put it, but it seems to go beyond the widget utility and into core app functionality.