From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "54191@debbugs.gnu.org" <54191@debbugs.gnu.org>
Subject: bug#54191: [External] : Re: bug#54191: 26.3; (elisp) `Magic File Names' FILENAME parameters: absolute names?
Date: Mon, 28 Feb 2022 17:22:11 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488B397CEAD3B42B89CBF4DF3019@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <835yozlyj8.fsf@gnu.org>
> They handle any kind of file names.
The question is how they handle them - how they
handle relative vs absolute names.
> > Users should be able to find out what
> > the behavior is in each case: relative or absolute.
>
> The behavior is the same: each function does its documented job and
> returns the advertised value.
It no doubt does what's documented. But if
what's documented is incomplete, then so will
be your understanding of what the function does.
> > > What each function _does_ with each kind of file name
> > > is a different matter.
> >
> > Yes, and that's exactly what I wrote about. The
> > behavior for each kind of file name should be
> > declared. That's the point of the bug report.
>
> Then there's no bug, because this particular function's behavior is
> documented.
In the doc string. Not in the manual.
And (for the Nth time), this bug report isn't
about "this particular function". I couldn't
be clearer about that.
>
> > > In the specific case of file-remote-p this is described
> > > both in the doc string and in the manual.
> >
> > No, not the manual, I think (unless it was added
> > recently).
>
> Yes, in the manual as well.
Where? As one reader, I don't see that.
And again, this bug report is _not_ about
`file-remote-p'.
> > That's what the bug report is about: doing just
> > what you said: describe what the function does
> > with each kind of file name.
>
> We already did.
I disagree. I wouldn't have filed the bug
report if that were the case.
next prev parent reply other threads:[~2022-02-28 17:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 21:30 bug#54191: 26.3; (elisp) `Magic File Names' FILENAME parameters: absolute names? Drew Adams
2022-02-27 22:42 ` Drew Adams
2022-02-28 8:03 ` Michael Albinus
2022-02-28 16:26 ` bug#54191: [External] : " Drew Adams
2022-03-01 11:55 ` Michael Albinus
2022-02-28 13:48 ` Eli Zaretskii
2022-02-28 16:26 ` bug#54191: [External] : " Drew Adams
2022-02-28 16:57 ` Eli Zaretskii
2022-02-28 17:22 ` Drew Adams [this message]
2022-02-28 9:33 ` Lars Ingebrigtsen
2022-02-28 16:28 ` bug#54191: [External] : " Drew Adams
2022-02-28 13:46 ` Eli Zaretskii
2022-02-28 16:26 ` bug#54191: [External] : " Drew Adams
2022-02-28 16:54 ` Eli Zaretskii
2022-02-28 17:22 ` Drew Adams
2022-02-28 17:44 ` Eli Zaretskii
2022-02-28 18:32 ` Drew Adams
2022-02-28 18:49 ` Eli Zaretskii
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=SJ0PR10MB5488B397CEAD3B42B89CBF4DF3019@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=54191@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.