Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Hugo Ishimaru
asdf
Commits
4f3907f3
Commit
4f3907f3
authored
May 05, 2014
by
Francois-Rene Rideau
Browse files
Trivial fix to the manual.
parent
4aa1c74e
Changes
1
Hide whitespace changes
Inline
Side-by-side
doc/asdf.texinfo
View file @
4f3907f3
...
...
@@ -1054,8 +1054,8 @@ This section begins with an example of a system definition,
then gives the full grammar of @code
{
defsystem
}
.
Let's look at a simple system.
This is a complete file that
w
ould
should be saved as @file
{
hello-lisp.asd
}
(in order that ASDF can find it
This is a complete file that
sh
ould
be saved as @file
{
hello-lisp.asd
}
(in order that ASDF can find it
when ordered to operate on the system named @code
{
"hello-lisp"
}
).
@c FIXME: the first example should have an outside dependency, e.g.,
...
...
@@ -1085,7 +1085,7 @@ helps make interactive development of @code{defsystem} forms behave in
the same was as when these forms are loaded by ASDF. If that's enough
for you, skip the rest of this item. Otherwise read on for the gory details.
If your file is loaded by ASDF 3, it will be loaded into the
If your file is loaded by ASDF 3, it will be loaded into the
@code
{
asdf-user
}
package. The @code
{
in-package
}
form
will ensure that the system definition is read the
same as within ASDF when you load it interactively with @code
{
cl:load
}
.
...
...
@@ -1097,7 +1097,7 @@ Recent versions of SLIME (2013-02 and later) know to do that.
@item
You can always rely on symbols
from both package @code
{
asdf
}
and @code
{
common-lisp
}
being available in
@code
{
.asd
}
files --
@code
{
.asd
}
files --
most importantly including @code
{
defsystem
}
.
@c FIXME: the following should be inserted in a more advanced
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment