Today, version 1.0.0 adds structured pipelines: a mechanism to exchange (almost) arbitrary objects via POSIX pipes, and transform them via external programs, shell builtins or Scheme code.
Example:
dir /proc | where name -starts k | sort-by modified
┌───────────┬────┬───────────────┬────────┐
│ name │type│ size │modified│
├───────────┼────┼───────────────┼────────┤
│kcore │file│140737471590400│09:32:44│
│kmsg │file│ 0│09:32:49│
│kallsyms │file│ 0│09:32:50│
│kpageflags │file│ 0│10:42:53│
│keys │file│ 0│10:42:53│
│kpagecount │file│ 0│10:42:53│
│key-users │file│ 0│10:42:53│
│kpagecgroup│file│ 0│10:42:53│
└───────────┴────┴───────────────┴────────┘
ip -j route | select dst dev prefsrc | to json1
[{"dst":"default","dev":"eth0"},
{"dst":"192.168.0.0/24","dev":"eth0","prefsrc":"192.168.0.2"}]
This allows arbitrary transformations at each pipeline step: filtering, choosing a subset of the fields, sorting with user-specified criteria, etc. And each step can be an executable program, a shell builtin or Scheme code.
If you know nushell, they will feel familiar as they are inspired by it - the implementation is fully independent, though.
> If you know nushell, they will feel familiar as they are inspired by it - the implementation is fully independent, though.
Looking deeper, there are two main differences:
- Nushell structured pipelines are an internal construct, and only work with nushell builtins. Schemesh uses actual POSIX pipes, which allows to also insert executables in the pipelines.
- schemesh also allows to insert arbitrary Scheme code in the pipelines. Nushell does too, in a sense: you have to write nushell language though
Nushell is great because it is really "battery included" in the sense that it ships with most of what you will ever need: http client (no need for curl), export/import of most formats (yaml, toml, csv, msgpack, sqlite, xml), etc. That really avoids the library or tool shopping problem. You can copy the 50MB nushell binary on almost anything and your script will work.
This is why this is really a "modern shell" as it includes what you need in 2026, not 1979.
This is also why I use nushell rather than python or lua for most scripts.
I am not familiar with the Scheme ecosystem but see you are implementing a lot within your shell (http client, sqlite support) what is great. But does that mean I can produce a Schemesh binary that will include Chez Scheme and run my script on any Linux or FreeBSD host?
Anyway I think what you are doing is really great !
Yes. Initially, I wanted to integrate http client, sqlite client etc. directly in the main shell executable.
This turned out to be impractical, because it introduces compile-time dependencies on external libraries, and because any bug, vulnerability or crash in the C code would bring down the whole shell.
My current solution is to have separate C programs (currently `http` and `parse_sqlite`) that are not compiled by default: you need to run `make utils` to build them.
> But does that mean I can produce a Schemesh binary that will include Chez Scheme and run my script on any Linux or FreeBSD host?
Yes, exactly. Schemesh is a C program that includes both Chez Scheme REPL and shell features.