GNU bug report logs - #54191
26.3; (elisp) `Magic File Names' FILENAME parameters: absolute names?

Previous Next

Full log

View this message in rfc822 format

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: "54191 <at> debbugs.gnu.org" <54191 <at> debbugs.gnu.org>
Subject: bug#54191: [External] : Re: bug#54191: 26.3; (elisp) `Magic File Names' FILENAME parameters: absolute names?
Date: Tue, 01 Mar 2022 12:55:05 +0100

Drew Adams <drew.adams <at> oracle.com> writes:

Hi Drew,


> Neither the manual nor the doc strings (except
> `file-remote-p', at least) state that the file name
> is expected to be absolute - or more precisely say
> what the behavior is for absolute vs relative.  But
> that info is important for using the functions, IMO.
>
> All I was saying there was that (1) the doc string
> of `file-remote-p' does in fact say what happens
> differently for a relative file name - which is good,
> helpful, and (2) I noticed this happy exception after
> filing the general report that the doc (strings &
> manual) generally does NOT mention what kind of file
> name is expected, for functions that accept a file name.
>
> That general lack is the reported bug.  That there
> are happy exceptions doesn't mean there aren't places
> where the doc (strings or manual or both) can be
> clarified to specify this.

Except the file-remote-p case, there is no need to say something special
about relative or absolute file names in case of file operations working
remotely. They simply work the same way in the local or remote case.

(If not it would be a bug.)

Best regards, Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.