Go to file
Timothy Sample 511dae3577 Add missing files to the distribution tarball.
* Makefile.am (EXTRA_DIST): Add various scripts, metadata, helpful
files, and tests.
2019-05-20 18:07:47 -04:00
build-aux Factor out and update the usual Guile rules. 2019-05-20 01:18:54 -04:00
doc Setup documentation generation. 2019-05-20 18:07:47 -04:00
gash Remove compression utility configuration. 2019-05-20 01:18:54 -04:00
scripts Remove (almost) all references to Geesh. 2019-05-20 01:17:40 -04:00
tests Fix test data filename. 2019-05-20 18:07:47 -04:00
tools Add copyright sign to headers. 2019-05-20 01:18:22 -04:00
.dir-locals.el Clean up '.dir-locals.el'. 2019-05-20 01:18:54 -04:00
.gitignore Setup documentation generation. 2019-05-20 18:07:47 -04:00
AUTHORS Update AUTHORS file. 2019-05-20 01:18:54 -04:00
COPYING Initial commit 2018-01-31 14:52:05 -05:00
ChangeLog Setup ChangeLog generation. 2019-05-20 01:18:54 -04:00
INSTALL Use the standard GNU INSTALL file. 2019-05-20 01:18:54 -04:00
Makefile.am Add missing files to the distribution tarball. 2019-05-20 18:07:47 -04:00
NEWS Add a NEWS file. 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 Remove 'foreign' Automake option. 2019-05-20 01:18:54 -04:00
guix.scm Setup documentation generation. 2019-05-20 18:07:47 -04: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