Hilbish has pretty standard job control. It’s missing one or two things, but works well. One thing which is different from other shells (besides Hilbish) itself is the API for jobs, and of course it’s in Lua. You can add jobs, stop and delete (disown) them and even get output.
Job Interface The job interface refers to hilbish.jobs.
Functions (Note that in the list here, they’re called from hilbish." property="og:description"><metacontent="(Thishasmainlybeenreplacedbyhilbish.jobs).
Hilbish has pretty standard job control. It’s missing one or two things, but works well. One thing which is different from other shells (besides Hilbish) itself is the API for jobs, and of course it’s in Lua. You can add jobs, stop and delete (disown) them and even get output.
Job Interface The job interface refers to hilbish.jobs.
<emclass=text-muted>by <strong>sammyette</strong></em><divclass=my-4><p>(This has mainly been replaced by <ahref=../api/hilbish.jobs>hilbish.jobs</a>
).</p><p>Hilbish has pretty standard job control. It’s missing one or two things,
but works well. One thing which is different from other shells
(besides Hilbish) itself is the API for jobs, and of course it’s in Lua.
You can add jobs, stop and delete (disown) them and even get output.</p><h2id=job-interfaceclass=heading>Job Interface
<ahref=#job-interfaceclass=heading-link><iclass="fas fa-paperclip"></i></a></h2><p>The job interface refers to <code>hilbish.jobs</code>.</p><h3id=functionsclass=heading>Functions
<ahref=#functionsclass=heading-link><iclass="fas fa-paperclip"></i></a></h3><p>(Note that in the list here, they’re called from <code>hilbish.jobs</code>, so
a listing of <code>foo</code> would mean <code>hilbish.jobs.foo</code>)</p><ul><li><code>all()</code> -> {jobs}: Returns a table of all jobs.</li><li><code>last()</code> -> job: Returns the last added job.</li><li><code>get(id)</code> -> job: Get a job by its ID.</li><li><code>add(cmdstr, args, execPath)</code> -> job: Adds a new job to the job table.
Note that this does not run the command; You have to start it manually.
<code>cmdstr</code> is the user’s input for the job, <code>args</code> is a table of arguments
for the command. It includes arg0 (don’t set it as entry 0 in the table)
and <code>execPath</code> is an absolute path for the command executable.</li><li><code>disown(id)</code>: Removes a job by ID from the job table.</li></ul><h2id=job-objectclass=heading>Job Object
<ahref=#job-objectclass=heading-link><iclass="fas fa-paperclip"></i></a></h2><p>A job object is a piece of <code>userdata</code>. All the functions of a job require
you to call them with a colon, since they are <em>methods</em> for the job object.
Example: hilbish.jobs.last():foreground()
Which will foreground the last job.</p><p>You can still have a job object for a disowned job,
it just won’t be <em>working</em> anywhere. :^)</p><h3id=propertiesclass=heading>Properties
<ahref=#propertiesclass=heading-link><iclass="fas fa-paperclip"></i></a></h3><ul><li><code>cmd</code>: command string</li><li><code>running</code>: boolean whether the job is running</li><li><code>id</code>: unique id for the job</li><li><code>pid</code>: process id for the job</li><li><code>exitCode</code>: exit code of the job
In ordinary cases you’d prefer to use the <code>id</code> instead of <code>pid</code>.
The <code>id</code> is unique to Hilbish and is how you get jobs with the
<code>hilbish.jobs</code> interface. It may also not describe the job entirely.</li></ul><h3id=functions-1class=heading>Functions
<ahref=#functions-1class=heading-link><iclass="fas fa-paperclip"></i></a></h3><ul><li><code>stop()</code>: Stops the job.</li><li><code>start()</code>: Starts the job.</li><li><code>foreground()</code>: Set the job as the current running foreground process, or
