From: Paul Eggert <eggert@cs.ucla.edu>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: thievol@posteo.net, 58919@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#58919: 28.2; dired-copy-file-recursive fails to overwrite directory
Date: Sun, 18 Dec 2022 12:54:59 -0800 [thread overview]
Message-ID: <4b4ed030-9a3e-1757-ec78-0ec770e261d9@cs.ucla.edu> (raw)
In-Reply-To: <87fsdcld2x.fsf@gmx.de>
On 12/18/22 11:35, Michael Albinus wrote:
> I re-read your make-directory code, it looks like
> PARENTS isn't propagated any longer to the file name handlers. So this
> must be handled documented there, at least.
Yes, the idea is that in Emacs 29, make-directory handlers never are
passed a non-nil PARENTS flag, and their return values are always
ignored. That way, Emacs 28 style make-directory handlers should work
fine in Emacs 29 since only the intersection of the Emacs 28 and 29
make-directory APIs is used when calling a make-directory handler.
In Emacs 30, once we've updated make-directory handlers to support the
Emacs 29 make-directory API, we can simplify the code that calls these
handlers.
next prev parent reply other threads:[~2022-12-18 20:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 8:54 bug#58919: 28.2; dired-copy-file-recursive fails to overwrite directory Thierry Volpiatto
2022-10-31 13:01 ` Eli Zaretskii
2022-11-01 17:34 ` Thierry Volpiatto
2022-11-01 18:04 ` Paul Eggert
2022-11-01 18:09 ` Eli Zaretskii
2022-11-01 19:21 ` Michael Albinus
2022-12-11 10:46 ` Eli Zaretskii
2022-12-16 23:22 ` Paul Eggert
2022-12-17 8:04 ` Eli Zaretskii
2022-12-17 9:52 ` Michael Albinus
2022-12-17 10:40 ` Eli Zaretskii
2022-12-17 22:40 ` Paul Eggert
2022-12-18 19:35 ` Michael Albinus
2022-12-18 20:54 ` Paul Eggert [this message]
2022-12-23 10:26 ` Michael Albinus
2022-12-24 9:11 ` Paul Eggert
2022-12-24 10: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b4ed030-9a3e-1757-ec78-0ec770e261d9@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=58919@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=thievol@posteo.net \
/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.