From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 54191@debbugs.gnu.org
Subject: bug#54191: 26.3; (elisp) `Magic File Names' FILENAME parameters: absolute names?
Date: Mon, 28 Feb 2022 15:48:54 +0200 [thread overview]
Message-ID: <83fso3m795.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB5488FB3D3C29E35846EE56CFF3009@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Sun, 27 Feb 2022 22:42:39 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> Date: Sun, 27 Feb 2022 22:42:39 +0000
>
> Users shouldn't have to search the Elisp code base
> to try to figure out whether they might need to
> apply `expand-file-name' to a file name before
> passing it to some function.
It goes without saying that _every_ file-related function in Emacs
accepts _any_ kind of file names: absolute, relative, you name it.
What each function _does_ with each kind of file name is a different
matter. In the specific case of file-remote-p this is described both
in the doc string and in the manual.
next prev parent reply other threads:[~2022-02-28 13:48 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 [this message]
2022-02-28 16:26 ` 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
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=83fso3m795.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54191@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.