Happy birthday Hilbish! As of last month, Hilbish is now 2 years old. +
Happy birthday Hilbish! As of last month, Hilbish is now 2 years old. Unfortunately I missed the official date, but I will still make a more focused post on the date (19st).
I decided to fix up this website and Hilbish's logo, so that can be thought of as something for the 2 years milestone?
Hilbish v2.0 has been released! +
Hilbish v2.0 has been released! Well actually, it was released a week ago, but I only wrote this Hilbish blog after that.
This is a *big* release, coming 9 months after the previous v1.2.0 and featuring over 40+ bug fixes and tons of new features and enhancements, so @@ -59,10 +59,10 @@ still hasn't reached levels of other alt shells in regards to literally everything, but the goal is to get there!
If you want to check the FULL changelog, you can do so here. This v2.0 release marks an advancement in Hilbish (and also how long one of my projects hasn't died) and I hope it can advance even further.
Thanks for reading, and I'll be back for the v2.1 release notes, or maybe -something else in between.
> The release with full changelogs and prebuilt binaries can be +
> The release with full changelogs and prebuilt binaries can be seen at the v2.1.0 tag.
Oh look! A new release of Hilbish! This time is the v2.1 release, with a small amount of features and mainly documentation changes and @@ -33,10 +33,10 @@ yet.
hilbish.completion.bins will no longer
cause a panic with all empty arguments passed.> The release with full changelogs and prebuilt binaries can be +
> The release with full changelogs and prebuilt binaries can be seen at the v2.1.1 tag.
Welcome to a fresh new release of Hilbish! Some people (or none) may be awaiting the long coming v2.2 release with lots of features, but I needed to push @@ -15,10 +15,10 @@ which results in less time wasted running invalid and TERRIBLE Lua code.
> The release with full changelogs and prebuilt binaries can be +
> The release with full changelogs and prebuilt binaries can be seen at the v2.1.2 tag.
This release reverts the April Fool's code additions in v2.1.1. It is functionally equal to v2.1.0. Nice!
A real release will come possibly in a few days or next week, so stay tuned for -the good and feature-filled release of v2.2!
> The release with full changelogs and prebuilt binaries can be +
> The release with full changelogs and prebuilt binaries can be seen at the v2.2.0 tag.
Welcome to a very long awaited release of Hilbish, and on Christmas. Just think of it as a long preparing, late Christmas gift. :) @@ -43,10 +43,10 @@ well now too due to an oversight when changing up the job functions.
> The release with full changelogs and prebuilt binaries can be +
> The release with full changelogs and prebuilt binaries can be seen at the v2.3.0 tag.
Hilbish v2.3 has now been released! This is small feature and bug fix release which took a while to cme ut since I took a long break from programming in general. @@ -24,10 +24,10 @@ they can now be exited. - The shell script interpreter now keeps its environment, and this also fixes the current working directory being wrong with some commands. - Some greenhouse bugs have been fixed, like randomly appearing when resizing the terminal -and some text attributes like color appearing where they weren't supposed to.
Hello! Welcome to the Hilbish blog. This will mainly contain release -announcements and some other things relating to Hilbish (development).
Bait is the event emitter for Hilbish. Much like Node.js and +
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
-pick a unique name!
\
Usage of the Bait module consists of userstanding
+pick a unique name!
Usage of the Bait module consists of userstanding
event-driven architecture, but it's pretty simple:
If you want to act on a certain event, you can catch it.
-You can act on events via callback functions.
\
Examples of this are in the Hilbish default config!
-Consider this part of it:
\
bait.catch('command.exit', function(code)
+You can act on events via callback functions.
Examples of this are in the Hilbish default config!
+Consider this part of it:bait.catch('command.exit', function(code)
running = false
doPrompt(code ~= 0)
doNotifyPrompt()
@@ -104,7 +104,7 @@ The arguments to pass to the hook.
Commander is the library which handles Hilbish commands. This makes +
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
-library in your Hilbish config.
lua
-local commander = require 'commander'
commander.register('hello', function(args, sinks) +library in your Hilbish config.
local commander = require 'commander'
+
+commander.register('hello', function(args, sinks)
sinks.out:writeln 'Hello world!'
end)
-In this example, a command with the name of hello is created
+
In this example, a command with the name of hello is created
that will print Hello world! to output. One question you may
have is: What is the sinks parameter?
The sinks parameter is a table with 3 keys: input, out, and err.
There is an in alias to input, but it requires using the string accessor syntax (sinks['in'])
as in is also a Lua keyword, so input is preferred for use.
All of them are a @Sink.
-In the future, sinks.in will be removed.
\
in is the standard input. You may use the read functions on this sink to get input from the user.
out is standard output. This is usually where command output should go.
err is standard error. This sink is for writing errors, as the name would suggest.
sinks.in will be removed.in is the standard input. You may use the read functions on this sink to get input from the user.
+- out is standard output. This is usually where command output should go.
+- err is standard error. This sink is for writing errors, as the name would suggest.