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:09 +0000 [thread overview]
Message-ID: <SJ0PR10MB54886A4D8371F706309350FEF3019@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <837d9flyo4.fsf@gnu.org>
> > > Did you follow the cross-reference? Because there you'd find the
> > > answer to your question, loud and clear.
> >
> > I don't think it does. No mention of absolute or
> > relative in that node.
>
> It _shows_ them.
I don't see any showing of a relative file name.
Can you point to one there?
> > And it's not just about `file-remote-p'. The
> > problem is more general, as reported. And the
> > general problem involves doc strings and manual.
>
> There's no more general problem here.
FILENAME in `Remote Files'
FILENAME and FILE in `Magic File Names'
FILENAME in `Visiting Functions'
FILENAME in `Subroutines of Visiting'
FILENAME in `Saving Buffers'
FILENAME in `Reading from Files'
FILENAME in `Writing to Files'
FILENAME and FILE in `File Locks'
...
and so on - lots of places.
Similarly, doc strings of functions that
accept file-name args. It's _not_ obvious
what the behavior is.
And yes, some functions do automatically
apply `expand-file-name' to a FILE(NAME) arg.
The question of whether a function does that,
and more generally how a function handles a
relative vs absolute file-name arg, is not
nothing.
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
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 [this message]
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=SJ0PR10MB54886A4D8371F706309350FEF3019@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.