manual: disambiguate meaning of "source"
This commit is contained in:
parent
373ef62e70
commit
e8c46cf058
1 changed files with 18 additions and 0 deletions
|
@ -306,6 +306,24 @@ If we did not avoid the second meaning of ``target'', then it would lead
|
||||||
to confusing language, such as describing Stow as installing symlinks
|
to confusing language, such as describing Stow as installing symlinks
|
||||||
into the target directory which point to targets @emph{outside} the
|
into the target directory which point to targets @emph{outside} the
|
||||||
target directory.
|
target directory.
|
||||||
|
|
||||||
|
Similarly, the word ``source'' can have two different meanings in this
|
||||||
|
context:
|
||||||
|
|
||||||
|
@enumerate
|
||||||
|
|
||||||
|
@item
|
||||||
|
the installation image, or some of its contents, and
|
||||||
|
|
||||||
|
@item
|
||||||
|
the location of symlinks (the ``source'' of the link, vs. its
|
||||||
|
destination).
|
||||||
|
|
||||||
|
@end enumerate
|
||||||
|
|
||||||
|
Therefore it should also be avoided, or at least care taken to ensure
|
||||||
|
that the meaning is not ambiguous.
|
||||||
|
|
||||||
@end quotation
|
@end quotation
|
||||||
|
|
||||||
@c ===========================================================================
|
@c ===========================================================================
|
||||||
|
|
Loading…
Reference in a new issue