Go to file
Timothy Sample c677ed85cc Clean up module imports in 'gash.scm'.
* gash/gash.scm: Sort the '#:use-module' lines and remove a duplicate
'(gash environment)'.
2019-05-20 01:18:54 -04:00
build-aux Build Gash with Autotools. 2019-05-16 10:49:16 -04:00
doc Merge branch 'gash' 2018-12-13 13:42:21 -05:00
gash Clean up module imports in 'gash.scm'. 2019-05-20 01:18:54 -04:00
scripts Remove (almost) all references to Geesh. 2019-05-20 01:17:40 -04:00
tests Add support for Guile 2.0. 2019-05-20 01:18:54 -04:00
tools Add copyright sign to headers. 2019-05-20 01:18:22 -04:00
.dir-locals.el Merge branch 'gash' 2018-12-13 13:42:21 -05:00
.gitignore Replace geesh script with gash. 2019-05-20 01:17:14 -04:00
AUTHORS Update AUTHORS. 2019-05-20 01:17:22 -04:00
COPYING Initial commit 2018-01-31 14:52:05 -05:00
INSTALL Remove (almost) all references to Geesh. 2019-05-20 01:17:40 -04:00
Makefile.am Stop 'make clean' from deleting tests. 2019-05-20 01:18:54 -04:00
README Initial commit 2018-01-31 14:52:05 -05:00
bootstrap Initial commit 2018-01-31 14:52:05 -05:00
configure.ac Add support for Guile 2.0. 2019-05-20 01:18:54 -04:00
guix.scm Remove (almost) all references to Geesh. 2019-05-20 01:17:40 -04:00
pre-inst-env.in Initial commit 2018-01-31 14:52:05 -05:00
test.sh Stabilize test suite. 2019-05-16 10:49:38 -04: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