From 823777b5337953d17b1814489532e40f1a2e96fc Mon Sep 17 00:00:00 2001 From: Xue Fuqiao Date: Tue, 11 Jun 2013 19:37:56 +0800 Subject: [PATCH] Make the example more intuitive. * doc/lispref/files.texi (File Name Expansion): Make the example more intuitive. --- doc/lispref/ChangeLog | 5 +++++ doc/lispref/files.texi | 13 ++++++++----- 2 files changed, 13 insertions(+), 5 deletions(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index c1a4f1e0729..259bf9a78a6 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,8 @@ +2013-06-11 Xue Fuqiao + + * files.texi (File Name Expansion): Make the example more + intuitive. + 2013-06-10 Paul Eggert Documentation fix for 'ls' and hard links. diff --git a/doc/lispref/files.texi b/doc/lispref/files.texi index c4d51ebbfe5..704ecfb6446 100644 --- a/doc/lispref/files.texi +++ b/doc/lispref/files.texi @@ -2105,10 +2105,6 @@ start with @samp{~}.) Otherwise, the current buffer's value of (expand-file-name "foo" "/usr/spool/") @result{} "/usr/spool/foo" @end group -@group -(expand-file-name "$HOME/foo") - @result{} "/xcssun/users/rms/lewis/$HOME/foo" -@end group @end example If the part of the combined file name before the first slash is @@ -2142,7 +2138,14 @@ This is for the sake of filesystems that have the concept of a @file{/../} is interpreted exactly the same as @file{/}. Note that @code{expand-file-name} does @emph{not} expand environment -variables; only @code{substitute-in-file-name} does that. +variables; only @code{substitute-in-file-name} does that: + +@example +@group +(expand-file-name "$HOME/foo") + @result{} "/xcssun/users/rms/lewis/$HOME/foo" +@end group +@end example Note also that @code{expand-file-name} does not follow symbolic links at any level. This results in a difference between the way -- 2.39.2