Continue tasks in background when window is closed

Bug #1083306 reported by Cassidy James Blaede on 2012-11-26
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Terminal
Confirmed
Wishlist
Unassigned

Bug Description

If tasks in the terminal are executing, the terminal app should continue tasks in the background when its window is closed. This way users can safely close the window and open it to come back to it later. If the task completes, the app should quit completely.

This helps further push us into the app-resumes-where-it-left-off territory and makes it so users can close the app at any time while allowing the task to continue, much like Noise.

If developers want an option to kill tasks when the window is closed, that could be a possibility.

Daniel Fore (danrabbit) on 2012-11-26
Changed in pantheon-terminal:
importance: Undecided → Wishlist
Changed in pantheon-terminal:
status: New → Confirmed
Hlobil Vaclav (vaclav-hlobil) wrote :

So, in this way, you just simply mask close button as minimize button? And user can much more likely to forgot about running processes in background (in minimized terminals)? Isn't it in a direct opposite of your argument, that minimized apps consume resources?

liamdawe (liamdawe) wrote :

How will you handle showing the background running has finished? As above its now just masking close as minimize.

David Gomes (davidgomes) on 2012-11-28
description: updated
Changed in pantheon-terminal:
milestone: none → 0.2

Ideally there would be a seperation of the app UI/window and the process itself. So closing the window would close the window (not mask it as minimize). Then when the process is done, it could shoot a notification.

David Gomes (davidgomes) on 2013-02-25
Changed in pantheon-terminal:
milestone: none → luna-beta3
Cody Garver (codygarver) on 2014-02-06
Changed in pantheon-terminal:
milestone: isis-beta1 → none
Daniel Fore (danrabbit) on 2016-05-21
Changed in pantheon-terminal:
milestone: none → loki+1-beta1
Zisu Andrei (matzipan) wrote :

I can think of at least one use case where this might not work: when an ssh session hangs.

Zisu Andrei (matzipan) wrote :

Actually wait, for hanging SSH sessions, you can just close the tab.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions