[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: file-readable-p returns t for empty string
From: |
Eli Zaretskii |
Subject: |
Re: file-readable-p returns t for empty string |
Date: |
Tue, 26 Feb 2002 20:59:04 +0200 |
> From: "=?ISO-8859-1?Q?J=E4rnestr=F6m Jonas?=" <erajonj@ki.ericsson.se>
> Date: Tue, 26 Feb 2002 19:46:05 +0100 (MET)
>
> (file-readable-p "") returns t.
> Wouldnt nil be more appropriate since there is no filename to visit
> (or whatever) despite the returning t?
> Same behavior for its peers like file-exists-p an so on...
That's because all these primitives call expand-file-name internally,
and expand-file-name returns the buffer's default directory when
passed an empty string as an argument.
I don't know off the top of my head why does expand-file-name do that.
- file-readable-p returns t for empty string, Järneström Jonas, 2002/02/26
- Re: file-readable-p returns t for empty string,
Eli Zaretskii <=
- Re: file-readable-p returns t for empty string, Richard Stallman, 2002/02/27
- Re: file-readable-p returns t for empty string, Richard Stallman, 2002/02/27
- Re: file-readable-p returns t for empty string, David Kastrup, 2002/02/28
- Re: file-readable-p returns t for empty string, Eli Zaretskii, 2002/02/28
- Re: file-readable-p returns t for empty string, David Kastrup, 2002/02/28
- Re: file-readable-p returns t for empty string, Eli Zaretskii, 2002/02/28
- Re: file-readable-p returns t for empty string, David Kastrup, 2002/02/28