background job management
Manage interactive jobs in Hilbish via Lua.
Jobs are the name of background tasks/commands. A job can be started via interactive usage or with the functions defined below for use in external runners.
add(cmdstr, args, execPath) | Creates a new job. This function does not run the job. This function is intended to be |
all() -> table[@Job] | Returns a table of all job objects. |
disown(id) | Disowns a job. This simply deletes it from the list of jobs without stopping it. |
get(id) -> @Job | Get a job object via its ID. |
last() -> @Job | Returns the last added job to the table. |
Creates a new job. This function does not run the job. This function is intended to be
used by runners, but can also be used to create jobs via Lua. Commanders cannot be ran as jobs.
string
cmdstr
String that a user would write for the job
table
args
Arguments for the commands. Has to include the name of the command.
string
execPath
Binary to use to run the command. Needs to be an absolute path.
1hilbish.jobs.add('go build', {'go', 'build'}, '/usr/bin/go')
Returns a table of all job objects.
This function has no parameters.
Disowns a job. This simply deletes it from the list of jobs without stopping it.
number
id
Returns the last added job to the table.
This function has no parameters.
The Job type describes a Hilbish job.
cmd | The user entered command string for the job. |
running | Whether the job is running or not. |
id | The ID of the job in the job table |
pid | The Process ID |
exitCode | The last exit code of the job. |
stdout | The standard output of the job. This just means the normal logs of the process. |
stderr | The standard error stream of the process. This (usually) includes error messages of the job. |
Puts a job in the background. This acts the same as initially running a job.
Puts a job in the foreground. This will cause it to run like it was executed normally and wait for it to complete.
Starts running the job.
Stops the job from running.
Want to help improve this page? Create an issue.