From 0a463e8c0c66d2ccedcabfb49b21a90899001af2 Mon Sep 17 00:00:00 2001 From: Adriano Peluso Date: Mon, 25 May 2020 11:52:45 +0200 Subject: [PATCH] doc: mentioning Guile Hall * doc/ref/scheme-using.texi (Using Guile Tools): add a subsection about Guile Hall --- doc/ref/scheme-using.texi | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi index ac265fcca..2c381743f 100644 --- a/doc/ref/scheme-using.texi +++ b/doc/ref/scheme-using.texi @@ -282,7 +282,7 @@ Run the optimizer on a piece of code and print the result. @deffn {REPL Command} disassemble exp Disassemble a compiled procedure. @end deffn - + @deffn {REPL Command} disassemble-file file Disassemble a file. @end deffn @@ -744,10 +744,31 @@ using a CPAN-like system. A complete list of guild scripts can be had by invoking @code{guild list}, or simply @code{guild}. +@menu +* Hall:: +@end menu + +@node Hall +@subsection Bootstrapping projects and distributing them + +There's a tool that doesn't come bundled with Guile and yet can be very +useful in your day to day experience with it. This tool is +@uref{https://gitlab.com/a-sassmannshausen/guile-hall, Hall}. + +When you start a new project, Hall creates a folder +containing a scaffold of your new project. +Such a scaffold will include your basic Autotools setup, so +you don't have to take care of that yourself. + +The scaffold contains a directory for your tests, +for your libraries, for your scripts and for +your documentation. So you immediately know where to put the +files you are hacking on. @node Installing Site Packages @section Installing Site Packages + @cindex site @cindex site path @cindex load path -- 2.25.1