ubuntu-phone team mailing list archive

[Sam Bull <sam.hacking@xxxxxxxx>]

Just had a thought on these special cases in the terminal. I'm still not
liking the idea of giving a lifecycle exception to the terminal, as I
don't think it's needed for most use cases.

But, what if we had a special command that would run a command in the
background. In the same manner that the sudo command runs any command as
a different user, another command (e.g. runbg) could run any command as
an external background running command.
	Presumably this command would do something along the lines of forking
the process so that it is not owned by the terminal app and thus not
dependent on the terminal to keep running. I'm not sure how complex this
is to implement, any thoughts on whether this would be a viable
approach?

On Fri, 2015-10-02 at 16:40 +0200, Thomas Voß wrote:
> Alan gave this example of compiling, doing mails and browsing at the
> *same* time. Obviously, the focus is on
> compiling here :) doing mails and browsing are just other tasks being
> executed at the same time. Now mail and browsing are certainly
> perfectly fine
> to be done on a phone. However, the scenario of compiling, checking
> mails and browsing in parallel (as in overlapping windowed mode) is
> not something
> very typically carried out in a mobile device usage scenario. The key
> point is: compiling would require uninterrupted execution in the
> background while
> switching from terminal to browser to mail client. Mail and browsing
> would still work, no problem with that. But: the full-blown scenario
> mentioned before is
> more of a desktop-ish use-case, which can happily be powered by the
> phone in docked mode. It's just a difference usage scenario.

Attachment: signature.asc
Description: This is a digitally signed message part