mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-05-20 11:40:18 +02:00
doc: Mention the former name of `guild'.
* doc/ref/scheme-using.texi (Using Guile Tools): Add a footnote mentioning that `guild' used to be `guile-tools'. * doc/ref/tools.texi (Executable Modules): Nitpicks.
This commit is contained in:
parent
715146aa15
commit
e108c961fe
2 changed files with 6 additions and 3 deletions
|
@ -704,7 +704,10 @@ information.
|
|||
Guile also comes with a growing number of command-line utilities: a
|
||||
compiler, a disassembler, some module inspectors, and in the future, a
|
||||
system to install Guile packages from the internet. These tools may be
|
||||
invoked using the @code{guild} program.
|
||||
invoked using the @code{guild} program@footnote{Until Guile version
|
||||
2.0.1, this program was known as @code{guile-tools}. The
|
||||
@code{guile-tools} executable is still installed as of 2.0.x but may be
|
||||
removed in a future stable series.}.
|
||||
|
||||
@example
|
||||
$ guild compile -o foo.go foo.scm
|
||||
|
|
|
@ -310,10 +310,10 @@ a regular Scheme module that has some additional packaging so that it can be
|
|||
used by guild, from the shell. For this reason, we sometimes use the
|
||||
term @dfn{script} in this context to mean the same thing.
|
||||
|
||||
As a convenience, the @code{guild} wrapper program is installed along w/
|
||||
As a convenience, the @code{guild} wrapper program is installed along with
|
||||
@code{guile}; it knows where a particular module is installed and calls it
|
||||
passing its args to the program. The result is that you need not augment your
|
||||
PATH. Usage is straightforward:
|
||||
@code{PATH}. Usage is straightforward:
|
||||
|
||||
@example
|
||||
guild --help
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue