the event emitter
the event emitter
Bait is the event emitter for Hilbish. Much like Node.js and
its events system, many actions in Hilbish emit events.
Unlike Node.js, Hilbish events are global. So make sure to
diff --git a/versions/snail/docs/api/commander/index.html b/versions/snail/docs/api/commander/index.html
index 3b6c65c..af2d8e9 100644
--- a/versions/snail/docs/api/commander/index.html
+++ b/versions/snail/docs/api/commander/index.html
@@ -1,7 +1,7 @@
library for custom commands
library for custom commands
Commander is the library which handles Hilbish commands. This makes the user able to add Lua-written commands to their shell without making a separate script in a bin folder. Instead, you may simply use the Commander diff --git a/versions/snail/docs/api/fs/index.html b/versions/snail/docs/api/fs/index.html index 691c5d7..25e569e 100644 --- a/versions/snail/docs/api/fs/index.html +++ b/versions/snail/docs/api/fs/index.html @@ -1,7 +1,7 @@
filesystem interaction and functionality library
filesystem interaction and functionality library
The fs module provides filesystem functions to Hilbish. While Lua’s standard
library has some I/O functions, they’re missing a lot of the basics. The fs
library offers more functions and will work on any operating system Hilbish does.
command aliasing
command aliasing
The alias interface deals with all command aliases in Hilbish.
| add(alias, cmd) | This is an alias (ha) for the hilbish.alias function. |
| delete(name) | Removes an alias. |
| list() -> table[string, string] | Get a table of all aliases, with string keys as the alias and the value as the command. |
| resolve(alias) -> string? | Resolves an alias to its original command. Will thrown an error if the alias doesn’t exist. |
tab completions
tab completions
The completions interface deals with tab completions.
| bins(query, ctx, fields) -> entries (table), prefix (string) | Return binaries/executables based on the provided parameters. |
| call(name, query, ctx, fields) -> completionGroups (table), prefix (string) | Calls a completer function. This is mainly used to call a command completer, which will have a name |
| files(query, ctx, fields) -> entries (table), prefix (string) | Returns file matches based on the provided parameters. |
| handler(line, pos) | This function contains the general completion handler for Hilbish. This function handles |
Return binaries/executables based on the provided parameters.
This function is meant to be used as a helper in a command completion handler.
interactions for Hilbish's line reader
interactions for Hilbish's line reader
The hilbish.editor interface provides functions to directly interact with the line editor in use.
| getLine() -> string | Returns the current input line. |
| getVimRegister(register) -> string | Returns the text that is at the register. |
| insert(text) | Inserts text into the Hilbish command line. |
| getChar() -> string | Reads a keystroke from the user. This is in a format of something like Ctrl-L. |
| setVimRegister(register, text) | Sets the vim register at register to hold the passed text. |
command history
command history
The history interface deals with command history. This includes the ability to override functions to change the main method of saving history.
background job management
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. |
native module loading
native module loading
The hilbish.module interface provides a function to load Hilbish plugins/modules. Hilbish modules are Go-written plugins (see https://pkg.go.dev/plugin diff --git a/versions/snail/docs/api/hilbish/hilbish.os/index.html b/versions/snail/docs/api/hilbish/hilbish.os/index.html index 592be9e..f0ee73b 100644 --- a/versions/snail/docs/api/hilbish/hilbish.os/index.html +++ b/versions/snail/docs/api/hilbish/hilbish.os/index.html @@ -1,7 +1,7 @@
operating system info
interactive command runner customization
interactive command runner customization
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 diff --git a/versions/snail/docs/api/hilbish/hilbish.timers/index.html b/versions/snail/docs/api/hilbish/hilbish.timers/index.html index c8c9b0a..b972b1c 100644 --- a/versions/snail/docs/api/hilbish/hilbish.timers/index.html +++ b/versions/snail/docs/api/hilbish/hilbish.timers/index.html @@ -1,7 +1,7 @@
timeout and interval API
timeout and interval API
If you ever want to run a piece of code on a timed interval, or want to wait a few seconds, you don’t have to rely on timing tricks, as Hilbish has a timer API to set intervals and timeouts.
These are the simple functions hilbish.interval and hilbish.timeout (doc
diff --git a/versions/snail/docs/api/hilbish/hilbish.userdir/index.html b/versions/snail/docs/api/hilbish/hilbish.userdir/index.html
index 33a5f73..922c03b 100644
--- a/versions/snail/docs/api/hilbish/hilbish.userdir/index.html
+++ b/versions/snail/docs/api/hilbish/hilbish.userdir/index.html
@@ -1,7 +1,7 @@
user-related directories
user-related directories
This interface just contains properties to know about certain user directories. It is equivalent to XDG on Linux and gets the user’s preferred directories for configs and data.
the core Hilbish API
the core Hilbish API
The Hilbish module includes the core API, containing interfaces and functions which directly relate to shell functionality.
| alias(cmd, orig) | Sets an alias, with a name of cmd to another command. |
| appendPath(dir) | Appends the provided dir to the command path ($PATH) |
| complete(scope, cb) | Registers a completion handler for the specified scope. |
| cwd() -> string | Returns the current directory of the shell. |
| exec(cmd) | Replaces the currently running Hilbish instance with the supplied command. |
| goro(fn) | Puts fn in a Goroutine. |
| highlighter(line) | Line highlighter handler. |
| hinter(line, pos) | The command line hint handler. It gets called on every key insert to |
| inputMode(mode) | Sets the input mode for Hilbish’s line reader. |
| interval(cb, time) -> @Timer | Runs the cb function every specified amount of time. |
| multiprompt(str) | Changes the text prompt when Hilbish asks for more input. |
| prependPath(dir) | Prepends dir to $PATH. |
| prompt(str, typ) | Changes the shell prompt to the provided string. |
| read(prompt) -> input (string) | Read input from the user, using Hilbish’s line editor/input reader. |
| run(cmd, streams) -> exitCode (number), stdout (string), stderr (string) | Runs cmd in Hilbish’s shell script interpreter. |
| runnerMode(mode) | Sets the execution/runner mode for interactive Hilbish. |
| timeout(cb, time) -> @Timer | Executed the cb function after a period of time. |
| which(name) -> string | Checks if name is a valid command. |
Welcome to the API documentation for Hilbish. This documents Lua functions +
Welcome to the API documentation for Hilbish. This documents Lua functions provided by Hilbish.
low level terminal library
low level terminal library
The terminal library is a simple and lower level library for certain terminal interactions.
| restoreState() | Restores the last saved state of the terminal |
| saveState() | Saves the current state of the terminal. |
| setRaw() | Puts the terminal into raw mode. |
| size() | Gets the dimensions of the terminal. Returns a table with width and height |
Restores the last saved state of the terminal
Tab completion for commands.
Completions for commands can be created with the hilbish.complete
+
Tab completion for commands.
Completions for commands can be created with the hilbish.complete
function. See the link for how to use it.
To create completions for a command is simple. The callback will be passed 3 parameters:
query (string): The text that the user is currently trying to complete.
This should be used to match entries.ctx (string): Contains the entire line. Use this if
diff --git a/versions/snail/docs/faq/index.html b/versions/snail/docs/faq/index.html
index 3ce5c7a..55c2ffd 100644
--- a/versions/snail/docs/faq/index.html
+++ b/versions/snail/docs/faq/index.html
@@ -5,7 +5,7 @@ Windows Support? It compiles for Windows (CI ensures it does), but otherwise it
Why? Hilbish emerged from the desire of a Lua configured shell." name=description>
Last updated Dec 26, 2023
Last updated Dec 26, 2023
No, it is not. POSIX compliance is a non-goal. Perhaps in the future, someone would be able to write a native plugin to support shell scripting (which would be against it’s main goal, but ….)
Last updated Dec 26, 2023
Hilbish has a wide range of features to enhance the user’s experience +
Last updated Dec 26, 2023
Hilbish has a wide range of features to enhance the user’s experience new ones are always being added. If there is something missing here or something you would like to see, please start a discussion or comment on any existing ones which match your request.
Last updated Dec 26, 2023
Get notified of shell actions.
Hilbish features a simple notification system which can be +
Last updated Dec 26, 2023
Get notified of shell actions.
Hilbish features a simple notification system which can be
used by other plugins and parts of the shell to notify the user
of various actions. This is used via the hilbish.message interface.
A message is defined as a table with the following properties:
icon: A unicode/emoji icon for the notification.title: The title of the messagetext: Message text/bodychannel: The source of the message. This should be a
unique and easily readable text identifier.summary: A short summary of the notification and message.
diff --git a/versions/snail/docs/features/opts/index.html b/versions/snail/docs/features/opts/index.html
index 3c4c9da..a7a4f72 100644
--- a/versions/snail/docs/features/opts/index.html
+++ b/versions/snail/docs/features/opts/index.html
@@ -1,7 +1,7 @@
Simple customizable options.
Opts are simple toggle or value options a user can set in Hilbish. +
Simple customizable options.
Opts are simple toggle or value options a user can set in Hilbish.
As toggles, there are things like autocd or history saving. As values,
there is the motd which the user can either change to a custom string or disable.
Opts are accessed from the hilbish.opts table. Here they can either
be read or modified
autocd
diff --git a/versions/snail/docs/features/runner-mode/index.html b/versions/snail/docs/features/runner-mode/index.html
index 160e64a..d086574 100644
--- a/versions/snail/docs/features/runner-mode/index.html
+++ b/versions/snail/docs/features/runner-mode/index.html
@@ -1,7 +1,7 @@
Last updated Dec 26, 2023
Customize the interactive script/command runner.
Hilbish allows you to change how interactive text can be interpreted. +
Last updated Dec 26, 2023
Customize the interactive script/command runner.
Hilbish allows you to change how interactive text can be interpreted. This is mainly due to the fact that the default method Hilbish uses is that it runs Lua first and then falls back to shell script.
In some cases, someone might want to switch to just shell script to avoid it while interactive but still have a Lua config, or go full Lua to use diff --git a/versions/snail/docs/getting-started/index.html b/versions/snail/docs/getting-started/index.html index 550385d..2a241c4 100644 --- a/versions/snail/docs/getting-started/index.html +++ b/versions/snail/docs/getting-started/index.html @@ -3,7 +3,7 @@ Setting as Default Login shell There are a few ways to make Hilbish your default Setting as Default Login shell There are a few ways to make Hilbish your default shell. A simple way is to make it your user/login shell." name=description>
Last updated Dec 26, 2023
To start Hilbish, open a terminal. If Hilbish has been installed and is not the +
Last updated Dec 26, 2023
To start Hilbish, open a terminal. If Hilbish has been installed and is not the
default shell, you can simply run hilbish to start it. This will launch
a normal interactive session.
To exit, you can either run the exit command or hit Ctrl+D.
Hilbish’s sample configuration is usually located in hilbish.dataDir .. '/.hilbishrc.lua'.
You can print that path via Lua to see what it is: print(hilbish.dataDir .. '/.hilbishrc.lua').
As an example, it will usually will result in /usr/share/hilbish/.hilbishrc.lua on Linux.
To edit your user configuration, you can copy that file to hilbish.userDir.config .. '/hilbish/init.lua',
-which follows XDG on Linux and MacOS, and is located in %APPDATA% on Windows.
As the directory is usually ~/.config on Linux, you can run this command to copy it:cp /usr/share/hilbish/.hilbishrc.lua ~/.config/hilbish/init.lua
Now you can get to editing it. Since it’s just a Lua file, having basic
-knowledge of Lua would help. All of Lua’s standard libraries and functions
-from Lua 5.4 are available. Hilbish has some custom and modules that are
-available. To see them, you can run the doc command. This also works as
-general documentation for other things.
As the directory is usually ~/.config on Linux, you can run this command to copy it:cp /usr/share/hilbish/.hilbishrc.lua ~/.config/hilbish/init.lua
Now we can get to customization!
If we closely examine a small snippet of the default config:
1-- Default Hilbish config
+ 2-- .. with some omitted code .. --
+ 3
+ 4local function doPrompt(fail)
+ 5 hilbish.prompt(lunacolors.format(
+ 6 '{blue}%u {cyan}%d ' .. (fail and '{red}' or '{green}') .. '∆ '
+ 7 ))
+ 8end
+ 9
+10doPrompt()
+11
+12bait.catch('command.exit', function(code)
+13 doPrompt(code ~= 0)
+14end)
+We see a whopping three Hilbish libraries being used in this part of code.
+First is of course, named after the shell itself, hilbish
+. This is kind of a
+“catch-all” namespace for functions that directly related to shell functionality/settings.
And as we can see, the hilbish.prompt +function is used +to change our prompt. Change our prompt to what, exactly?
The doc for the function states that the verbs %u and %dare used for username and current directory
+of the shell, respectively.
We wrap this in the lunacolors.format
+function, to give
+our prompt some nice color.
But you might have also noticed that this is in the doPrompt function, which is called once,
+and then used again in a bait
+hook. Specifically, the command.exit hook,
+which is called after a command exits, so when it finishes running.
Thrown right before a command is executed.
string input
The raw string that the user typed. This will include the text
without changes applied to it (argument substitution, alias expansion,
diff --git a/versions/snail/docs/hooks/hilbish/index.html b/versions/snail/docs/hooks/hilbish/index.html
index c2b09f3..2ad5ff3 100644
--- a/versions/snail/docs/hooks/hilbish/index.html
+++ b/versions/snail/docs/hooks/hilbish/index.html
@@ -11,7 +11,7 @@ The mode that has been set. Can be these values: insert, normal, delete or repla
hilbish.cancel Sent when the user cancels their command input with Ctrl-C" name=description>
Sent when Hilbish is going to exit.
This signal returns no variables.
Sent when the Vim mode of Hilbish is changed (like from insert to normal mode). diff --git a/versions/snail/docs/hooks/index.html b/versions/snail/docs/hooks/index.html index 58e52d3..fdb4c91 100644 --- a/versions/snail/docs/hooks/index.html +++ b/versions/snail/docs/hooks/index.html @@ -1,6 +1,6 @@
Signals are global events emitted with the Bait module. For more detail on how to use these signals, you may check the Bait page.
Thrown when Hilbish receive the SIGINT signal, aka when Ctrl-C is pressed.
This signal returns no variables.
Last updated Dec 26, 2023
Hilbish is a hyper-extensible shell mainly intended for interactive use. +
Last updated Dec 26, 2023
Hilbish is a hyper-extensible shell mainly intended for interactive use. To enhance the interactive experience, Hilbish comes with a wide range of features and sane defaults, including a nice looking prompt, advanced completion menus and history search.
Here documents some of the features of Hilbish and the Lua API.
Lunacolors is an ANSI color/styling library for Lua. It is included +
Lunacolors is an ANSI color/styling library for Lua. It is included by default in standard Hilbish distributions to provide easy styling for things like prompts and text.
For simple usage, a single color or style is enough. For example,
you can just use lunacolors.blue 'Hello world' and that’ll return
diff --git a/versions/snail/docs/nature/dirs/index.html b/versions/snail/docs/nature/dirs/index.html
index bb0c76e..1bfcce8 100644
--- a/versions/snail/docs/nature/dirs/index.html
+++ b/versions/snail/docs/nature/dirs/index.html
@@ -1,12 +1,16 @@
-
No description.
internal directory management
The dirs module defines a small set of functions to store and manage +directories.
| recent(idx) | Get entry from recent directories list based on index. |
| pop(num) | Remove the specified amount of dirs from the recent directories list. |
| peak(num) | Look at num amount of recent directories, starting from the latest. |
| push(dir) | Add dir to the recent directories list. |
| setOld(d) | Sets the old directory string. |
Look at num amount of recent directories, starting from the latest.
d string
Look at num amount of recent directories, starting from the latest.
+This returns a table of recent directories, up to the num amount.
num number
Remove the specified amount of dirs from the recent directories list.
num number
command-line doc rendering
The doc module contains a small set of functions +used by the Greenhouse pager to render parts of the documentation pages. +This is only documented for the sake of it. It’s only intended use +is by the Greenhouse pager.
| renderCodeBlock(text) | Assembles and renders a code block. This returns |
| highlight(text) | Performs basic Lua code highlighting. |
| renderInfoBlock(type, text) | Renders an info block. An info block is a block of text with |
Renders an info block. An info block is a block of text with +an icon and styled text block.
type string
Type of info block. The only one specially styled is the warning.
text string
Performs basic Lua code highlighting.
text string
Code/text to do highlighting on.
A bit after creation, we have the outside nature. Little plants, seeds, +
A bit after creation, we have the outside nature. Little plants, seeds,
growing to their final phase: a full plant. A lot of Hilbish itself is
written in Go, but there are parts made in Lua, being most builtins
(doc, cd, cdr), completions, and other things.
Hilbish’s Lua core module is called nature.
diff --git a/versions/snail/docs/nature/index.xml b/versions/snail/docs/nature/index.xml
index 46b20a1..a4bddce 100644
--- a/versions/snail/docs/nature/index.xml
+++ b/versions/snail/docs/nature/index.xml
@@ -1,10 +1,3 @@
-
Vim actions are essentially just when a user uses a Vim keybind. +
Vim actions are essentially just when a user uses a Vim keybind. Things like yanking and pasting are Vim actions. This is not an “offical Vim thing,” just a Hilbish thing.
The hilbish.vimAction hook is thrown whenever a Vim action occurs.
It passes 2 arguments: the action name, and an array (table) of args
diff --git a/versions/snail/docs/vim-mode/index.html b/versions/snail/docs/vim-mode/index.html
index dd65a7a..7be4b15 100644
--- a/versions/snail/docs/vim-mode/index.html
+++ b/versions/snail/docs/vim-mode/index.html
@@ -3,5 +3,5 @@ This is documentation for everything relating to it." property="og:description">
This is documentation for everything relating to it." name=description>
Hilbish has a Vim binding input mode accessible for use. +
Hilbish has a Vim binding input mode accessible for use.
It can be enabled with the hilbish.inputMode function (check doc hilbish).
This is documentation for everything relating to it.