janetsh icon indicating copy to clipboard operation
janetsh copied to clipboard

A powerful new shell that uses the janet programming language for both the implementation and repl.

Results 43 janetsh issues
Sort by recently updated
recently updated
newest added

A standalone single file binary might be useful for some people, static linking would be very nice. Technically, can be done easily, it just is a matter of some boring...

enhancement

& style redirects are perhaps are not needed: ``` foo :2>&1 ``` Would become any of the forms below: ``` :2> '1 :2> [1] ```

enhancement
maybe
breaking

It doesn't make sense to make users load it.

Users can just import without a prefix, or make their own aliases in an rc file.

enhancement
refactor
breaking

Compiling the completion logic doesn't make sense when running scripts. We should do a lazy import if possible. This makes it possible for even more sophisticated completions without worrying about...

enhancement
maybe
performance

It may be desirable to explicitly allow and write tests for things like: ``` ($ (fn [table] (pp table)) @{"foo" "bar"}) @{"foo" "bar"} ``` Because a function is not an...

enhancement
maybe

It is a bit confusing to run janetsh without installing it because janetsh does not have a PATH setup so you need to run it form the src dir. We...

enhancement

``` (sh/alias "foo" (fn [&args] (print "foo"))) ``` should work. Currently it doesn't due to excessive stringification. The current work around is to manually add entries to the *aliases* table....

bug
maybe
rare

We do one stat to check if something is a directory, then another to check if the file is what we want, and possibly more. We could refactor to fix...

enhancement
refactor
performance

``` touch [@{1 2 3 4}] ``` currently makes a file like: '' It would be better to just crash the child in this case, the user obviously did not...

bug