From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Michael Albinus <michael.albinus@gmx.de>,
Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: master e315544: ; * src/fileio.c (Fdirectory_append): Doc fix.
Date: Sun, 25 Jul 2021 15:05:43 +0200 [thread overview]
Message-ID: <875ywy7dco.fsf@gmail.com> (raw)
In-Reply-To: <8735s262a7.fsf@igel.home> (Andreas Schwab's message of "Sun, 25 Jul 2021 13:50:08 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
>> -*** New function 'directory-append'.
>> -This appends a file name to a directory name and returns the result.
>> +*** New function 'file-name-concat'.
>> +This appends path components to a directory name and returns the result.
>
> s/path/file name/
Fair enough; I shied away from the three-word compound, but I see now
that we have "(elisp) File Name Components".
diff --git a/etc/NEWS b/etc/NEWS
index 0d1abfd852..ce34236500 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -3110,7 +3110,8 @@ The former is now declared obsolete.
+++
*** New function 'file-name-concat'.
-This appends path components to a directory name and returns the result.
+This appends file name components to a directory name and returns the
+result.
+++
*** New function 'split-string-shell-command'.
> This should probably emphasize the fact that it ignores file name
> handlers.
The NEWS entry specifically, or the docstring and/or info entry?
next prev parent reply other threads:[~2021-07-25 13:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210724171858.1726.43078@vcs0.savannah.gnu.org>
[not found] ` <20210724171900.4A26D20D0A@vcs0.savannah.gnu.org>
2021-07-24 18:39 ` master e315544: ; * src/fileio.c (Fdirectory_append): Doc fix Michael Albinus
2021-07-24 18:51 ` Lars Ingebrigtsen
2021-07-24 19:04 ` Michael Albinus
2021-07-25 5:19 ` Lars Ingebrigtsen
2021-07-25 5:27 ` Stefan Monnier
2021-07-25 6:54 ` Lars Ingebrigtsen
2021-07-25 10:01 ` Kévin Le Gouguec
2021-07-25 10:23 ` Lars Ingebrigtsen
2021-07-25 11:50 ` Andreas Schwab
2021-07-25 13:05 ` Kévin Le Gouguec [this message]
2021-07-28 15:39 ` Lars Ingebrigtsen
2021-07-28 17:28 ` Michael Albinus
2021-07-30 11:36 ` Lars Ingebrigtsen
2021-07-25 7:59 ` Michael Albinus
2021-07-28 15:36 ` Lars Ingebrigtsen
2021-07-28 17:13 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ywy7dco.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).