GNU bug report logs -
#18318
24.4.50; doc of `file-readable-p'
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Fri, 22 Aug 2014 21:15:02 UTC
Severity: wishlist
Tags: wontfix
Found in version 24.4.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18318 in the body.
You can then email your comments to 18318 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18318
; Package
emacs
.
(Fri, 22 Aug 2014 21:15:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 22 Aug 2014 21:15:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
The doc - both Elisp manual and doc string, should explicitly point out
that this returns non-nil for a directory, IOW, a non-nil value does not
mean that the file can be, say, inserted into a buffer.
In addition, it would be better to change the parameter name to
FILE-OR-DIR (or even FILE-OR-DIR-NAME). It is all to easy to not
realize, when reading this, that this does not test for a non-directory
file that is readable.
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-06-28 on ODIEONE
Bzr revision: 117431 rgm <at> gnu.org-20140628015517-eku6hj8mpgcvfnso
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/snapshot/trunk
--enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
-Ic:/Devel/emacs/include''
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18318
; Package
emacs
.
(Sat, 30 Apr 2016 13:40:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 18318 <at> debbugs.gnu.org (full text, mbox):
Drew Adams <drew.adams <at> oracle.com> writes:
> The doc - both Elisp manual and doc string, should explicitly point out
> that this returns non-nil for a directory, IOW, a non-nil value does not
> mean that the file can be, say, inserted into a buffer.
>
> In addition, it would be better to change the parameter name to
> FILE-OR-DIR (or even FILE-OR-DIR-NAME). It is all to easy to not
> realize, when reading this, that this does not test for a non-directory
> file that is readable.
Well, the function isn't about files or directories, but filenames. It
can be a fifo, a device node, etc. So I think the doc is fine as it is.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) wontfix.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 30 Apr 2016 13:40:02 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
18318 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 30 Apr 2016 13:40:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18318
; Package
emacs
.
(Sat, 30 Apr 2016 16:08:02 GMT)
Full text and
rfc822 format available.
Message #15 received at 18318 <at> debbugs.gnu.org (full text, mbox):
> > The doc - both Elisp manual and doc string, should explicitly point out
> > that this returns non-nil for a directory, IOW, a non-nil value does not
> > mean that the file can be, say, inserted into a buffer.
> >
> > In addition, it would be better to change the parameter name to
> > FILE-OR-DIR (or even FILE-OR-DIR-NAME). It is all to easy to not
> > realize, when reading this, that this does not test for a non-directory
> > file that is readable.
>
> Well, the function isn't about files or directories, but filenames. It
> can be a fifo, a device node, etc.
All the more reason to make the doc clearer. The argument
passed to the function is not necessarily the name of a file
whose contents can, say, be inserted into a buffer. It is
not a FILENAME, unless you understand "filename" in the wider
sense you elaborated - elaboration that is missing from this doc.
It is (I think) far more common for a file or directory name
(string) to be passed as an argument than it is for a FIFO,
device node, etc. to be passed. The directory case is common,
and the doc misleads. If you want to mention other
possibilities, besides file and dir names, so much the better.
But ideal should not be the enemy of better.
> So I think the doc is fine as it is.
Disagree.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18318
; Package
emacs
.
(Sat, 30 Apr 2016 16:26:01 GMT)
Full text and
rfc822 format available.
Message #18 received at 18318 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 30 Apr 2016 08:07:31 -0800 (GMT-08:00)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: 18318 <at> debbugs.gnu.org
>
> It is (I think) far more common for a file or directory name
> (string) to be passed as an argument than it is for a FIFO,
> device node, etc. to be passed. The directory case is common,
> and the doc misleads.
Why do you say it misleads? A directory is just a kind of file (the
manual explains that, if the user doesn't already know). So I see
nothing misleading here.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18318
; Package
emacs
.
(Sat, 30 Apr 2016 17:33:02 GMT)
Full text and
rfc822 format available.
Message #21 received at 18318 <at> debbugs.gnu.org (full text, mbox):
> > It is (I think) far more common for a file or directory name
> > (string) to be passed as an argument than it is for a FIFO,
> > device node, etc. to be passed. The directory case is common,
> > and the doc misleads.
>
> Why do you say it misleads? A directory is just a kind of file (the
> manual explains that, if the user doesn't already know). So I see
> nothing misleading here.
Sure, a directory is also a file. But it is a special kind
of file. What is misleading is that a reader might well not
think that a directory name will return a non-nil value, and
so assume that s?he can do things with it such as insert its
contents in a buffer etc.
It's about being a bit clearer; that's all.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#18318
; Package
emacs
.
(Sat, 30 Apr 2016 18:24:01 GMT)
Full text and
rfc822 format available.
Message #24 received at 18318 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 30 Apr 2016 09:32:01 -0800 (GMT-08:00)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: larsi <at> gnus.org, 18318 <at> debbugs.gnu.org
>
> What is misleading is that a reader might well not think that a
> directory name will return a non-nil value, and so assume that s?he
> can do things with it such as insert its contents in a buffer etc.
And she can, indeed, at least on some systems.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 29 May 2016 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 9 years and 107 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.