comparison lispref/files.texi @ 77361:916f8aa2138d

(File Name Expansion): Clarify previous change.
author Richard M. Stallman <rms@gnu.org>
date Sat, 21 Apr 2007 08:58:15 +0000
parents 95a196e2e465
children cf24d1dc433c 6b44d05a5f0b e6fdae9180d4
comparison
equal deleted inserted replaced
77360:467b5b7572bd 77361:916f8aa2138d
1988 (expand-file-name "bar/../foo") 1988 (expand-file-name "bar/../foo")
1989 @result{} "/xcssun/users/rms/lewis/foo" 1989 @result{} "/xcssun/users/rms/lewis/foo"
1990 @end group 1990 @end group
1991 @end example 1991 @end example
1992 1992
1993 In some cases, a leading @samp{..} can remain in the output: 1993 In some cases, a leading @samp{..} component can remain in the output:
1994 1994
1995 @example 1995 @example
1996 @group 1996 @group
1997 (expand-file-name "../home" "/") 1997 (expand-file-name "../home" "/")
1998 @result{} "/../home" 1998 @result{} "/../home"
1999 @end group 1999 @end group
2000 @end example 2000 @end example
2001 2001
2002 This is for use with filesystems that have the concept of a 2002 @noindent
2003 This is for the sake of filesystems that have the concept of a
2003 ``superroot'' above the root directory @file{/}. On other filesystems, 2004 ``superroot'' above the root directory @file{/}. On other filesystems,
2004 @file{/../} is interpreted exactly the same as @file{/}. 2005 @file{/../} is interpreted exactly the same as @file{/}.
2005 2006
2006 Note that @code{expand-file-name} does @emph{not} expand environment 2007 Note that @code{expand-file-name} does @emph{not} expand environment
2007 variables; only @code{substitute-in-file-name} does that. 2008 variables; only @code{substitute-in-file-name} does that.