From: yk.9fans@icloud.com (Yaroslav Kolomiiets)
Subject: [9fans] Backgrounding a task
Date: Mon, 23 Oct 2017 20:20:50 +0300 [thread overview]
Message-ID: <9D87888B-7BCA-4B26-BA2B-AAF2FFB04FE7@icloud.com> (raw)
In-Reply-To: <587079C0-5E5F-4781-BBEF-3B2BDEADED7F@gmail.com>
?window -m cmd? will run the command in the same namespace, forked, but in new window.
?-m? is for ?mount?, an alternative way of communication with the window system to /dev/wctl which is default.
Yaroslav Kolomiiets
7 ????. 2017 ?. ? 15:21 Chris McGee <newton688 at gmail.com> ????:
Thanks for the tip! I'll give that a try.
Chris
? ??????????
> On Oct 7, 2017, at 12:04 AM, Skip Tavakkolian <skip.tavakkolian at gmail.com> wrote:
>
> Spitballing here: in the new window do something like
>
> cat /proc/123/ns | rc
>
> Or first massage the ns then generate an output for rc.
>
>> On Fri, Oct 6, 2017, 4:34 PM Chris McGee <newton688 at gmail.com> wrote:
>> Hi All,
>>
>> When I'm using Unix, there's a workflow that I use for long running commands that I'm hoping to find the equivalent in the Plan 9 way of doing things.
>>
>> I will occasionally run a command, realize that it will take a long time to complete. I don't want to kill it. I'll just Ctrl-Z and bg to put it into the background using the shell. It's almost as if I had run it with '&' in the first place. I can then run other commands in the same working directory, environment and shell history.
>>
>> Is there an equivalent to this workflow in Plan 9?
>>
>> I realize that the whole job control system dates back to old single session terminals, which isn't a problem with Rio where you can draw new windows at will. Initially I thought, that you just drag that window to a corner somewhere and let it complete. But, if I draw a new window it won't be in the same working directory, have the same environment and namespace. Maybe there is a way to create a window that inherits these from an existing process?
>>
>> Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.9fans.net/private/9fans/attachments/20171023/bf889239/attachment.html>
next prev parent reply other threads:[~2017-10-23 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 23:33 Chris McGee
2017-10-07 1:42 ` Erik Quanstrom
2017-10-07 4:04 ` Skip Tavakkolian
2017-10-07 12:21 ` Chris McGee
2017-10-23 17:20 ` Yaroslav Kolomiiets [this message]
2017-10-24 1:48 ` Chris McGee
2017-10-24 3:54 Alex Musolino
2017-10-24 11:19 ` Chris McGee
2017-10-24 14:21 Alex Musolino
2017-10-24 19:18 ` Giacomo Tesio
2017-10-24 22:07 ` Giacomo Tesio
2017-10-24 23:00 ` Chris McGee
2017-10-24 23:13 ` Giacomo Tesio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9D87888B-7BCA-4B26-BA2B-AAF2FFB04FE7@icloud.com \
--to=yk.9fans@icloud.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).