You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
directory-exists-p returns non nil for strings that are interpreted as existing directory names, as "" or ".." in unix (the documentation says: "Checks whether the file named by the pathname designator pathspec exists and if it is a directory"). Similarly, (pathname-absolute-p "") return T, or (pathname-relative-p "..") returns T, etc.
directory-pathname-p instead returns nil for unix directory names as "~" or "..", and this is counter-intuitive given the above results. I think that this functions should returns the same result as directory-exists-p for those special strings, since they are valid directory pathnames (at least in unix-like notation).
The text was updated successfully, but these errors were encountered:
directory-exists-p returns non nil for strings that are interpreted as existing directory names, as "
" or ".." in unix (the documentation says: "Checks whether the file named by the pathname designator pathspec exists and if it is a directory"). Similarly, (pathname-absolute-p "") return T, or (pathname-relative-p "..") returns T, etc.directory-pathname-p instead returns nil for unix directory names as "~" or "..", and this is counter-intuitive given the above results. I think that this functions should returns the same result as directory-exists-p for those special strings, since they are valid directory pathnames (at least in unix-like notation).
The text was updated successfully, but these errors were encountered: