Go to file
Jan Nieuwenhuizen 992e12444d chmod: New builtin.
* gash/commands/chmod.scm: New file.
* build-aux/build-guile.sh: Compile it.
* .gitignore: Ignore it.
2018-11-05 19:59:53 +01:00
bin builtins: Split out into gash/commands/. 2018-11-03 08:02:49 +01:00
build-aux chmod: New builtin. 2018-11-05 19:59:53 +01:00
doc doc: Add skeleton. 2018-07-10 00:11:50 +02:00
gash chmod: New builtin. 2018-11-05 19:59:53 +01:00
test test: tar. 2018-11-05 19:59:53 +01:00
todo guix: resurrect package build. 2018-07-10 00:11:24 +02:00
.dir-locals.el Geiser support. 2018-07-04 20:11:26 +02:00
.gitignore chmod: New builtin. 2018-11-05 19:59:53 +01:00
AUTHORS builtins: Split out into gash/commands/. 2018-11-03 08:02:49 +01:00
COPYING Add GPL. 2017-12-07 23:07:27 +01:00
INSTALL geesh: initial integration. 2018-10-21 12:45:51 +02:00
README complete rename from anguish to gash 2017-12-07 23:07:31 +01:00
TODO WIP: marginal 2018-07-14 12:34:42 +02:00
check.sh test: tar. 2018-11-05 19:59:53 +01:00
configure chmod: New builtin. 2018-11-05 19:59:53 +01:00
guix.scm doc: Add skeleton. 2018-07-10 00:11:50 +02:00
makefile test: tar. 2018-11-05 19:59:53 +01:00
sh.bnf PEG shell grammar. 2017-12-07 23:07:27 +01:00
test.sh test: Update test suite. 2018-11-05 19:59:53 +01:00

README

This project aims to produce at least a POSIX compliant sh replacement
or even implement GNU bash.  On top of that it also intends to make
scheme available for interactive and scripting application.  The
approach also intends to allow capturing the intermediate scheme
representation of the "original" shell script to offer a migration
path away from [ba]sh. On top of this GNU make could similarly be
replaced, as make turns out to be fraught with limitations and
complexities.  One of the features I personally desire is not be
forced to keep doing what was done in the past, i.e. once an object
file is produced, it does not have to be produced again as long as the
original is kept around. The orignal must be replaced when any of its
dependencies change (source, compiler options, linker, etc.)

I feel that the shell has been instrumental on my path to embracing
functional programming, however now I mostly experience that the
language itselfs folds on functional expression, pun intended.


* history flattened vs full, i.e. navigate interactively without
  redundancy vs export as script