From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 56673@debbugs.gnu.org
Subject: bug#56673: 26.3; Doc of `file-equal-p'
Date: Thu, 21 Jul 2022 19:30:59 +0300 [thread overview]
Message-ID: <83czdymnr0.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB548829717389BC4F454A465DF3919@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Thu, 21 Jul 2022 16:12:29 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> CC: "56673-done@debbugs.gnu.org" <56673-done@debbugs.gnu.org>
> Date: Thu, 21 Jul 2022 16:12:29 +0000
>
> Do you disagree that that's the only case?
It doesn't matter for the purposes of this discussion, such as it is.
> If that's the only case, then could we perhaps say
> something like this (statement, not wording)?
>
> If neither file name has a `file-equal-p' handler
> then if either file does not exist the return
> value is nil.
>
> If either name has a `file-equal-p' handler then
> the return value could be nil or non-nil when
> either file does not exist.
It is not useful to write such documentation because there's no easy
way to know up front which file will have a handler and which won't.
(If you think only remote files have handlers, think again.)
> > > This is similar to comparing their truenames, except that
> > > remote file names are also handled in an appropriate manner.
> >
> > The doc string already says that, albeit with different words.
>
> I don't see how it even vaguely suggests that,
> in any way. Could you point to the wording you
> think "already says that"?
Sorry, I dreamed it.
prev parent reply other threads:[~2022-07-21 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 20:41 bug#56673: 26.3; Doc of `file-equal-p' Drew Adams
2022-07-21 5:59 ` Eli Zaretskii
2022-07-21 16:12 ` Drew Adams
2022-07-21 16:30 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83czdymnr0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56673@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.