Module hilbish.runner

interactive command runner customization

Introduction

The runner interface contains functions that allow the user to change how Hilbish interprets interactive input. Users can add and change the default runner for interactive input to any language or script of their choosing. A good example is using it to write command in Fennel.

Runners are functions that evaluate user input. The default runners in Hilbish can run shell script and Lua code.

A runner is passed the input and has to return a table with these values. All are not required, only the useful ones the runner needs to return. (So if there isn’t an error, just omit err.)

• exitCode (number): Exit code of the command
• input (string): The text input of the user. This is used by Hilbish to append extra input, in case more is requested.
• err (string): A string that represents an error from the runner. This should only be set when, for example, there is a syntax error. It can be set to a few special values for Hilbish to throw the right hooks and have a better looking message.
  • \<command>: not-found will throw a command.not-found hook based on what \<command> is.
  • \<command>: not-executable will throw a command.not-executable hook.
• continue (boolean): Whether Hilbish should prompt the user for no input
• newline (boolean): Whether a newline should be added at the end of input.

Here is a simple example of a fennel runner. It falls back to shell script if fennel eval has an error.

 1local fennel = require 'fennel'
 2
 3hilbish.runnerMode(function(input)
 4	local ok = pcall(fennel.eval, input)
 5	if ok then
 6		return {
 7			input = input
 8		}
 9	end
10
11	return hilbish.runner.sh(input)
12end)

Functions