[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Documentation of `file-name-completion' is somewhat confusing
From: |
Eli Zaretskii |
Subject: |
Re: Documentation of `file-name-completion' is somewhat confusing |
Date: |
Wed, 12 Jun 2013 05:58:41 +0300 |
> Date: Wed, 12 Jun 2013 10:07:37 +0800
> From: Xue Fuqiao <address@hidden>
>
> In (info "(elisp) File Name Completion"):
> -- Function: file-name-completion filename directory &optional
> predicate
> [...]
> If PREDICATE is non-`nil' then it ignores possible completions that
> don't satisfy PREDICATE, after calling that function with one
> argument, the expanded absolute file name.
>
> And in the doc string of this function:
> If PREDICATE is non-nil, call PREDICATE with each possible
> completion (in absolute form) and ignore it if PREDICATE returns
> nil.
>
> It seems to me that the arguments of PREDICATE described by these two
> paragraphs don't agree with each other: the first one is "the expanded
> absolute file name", but the second one is "each possible completion".
> IMHO the latter is more appropriate. Or maybe I got something wrong.
> Any ideas?
Why do you think that "expanded absolute file name" of a "possible
completion" and "each possible completion (in absolute form)" are
anything but the same thing? Where exactly do you see the difference
between these two?