unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: thievol@posteo.net, 58919@debbugs.gnu.org,
	Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#58919: 28.2; dired-copy-file-recursive fails to overwrite directory
Date: Sat, 17 Dec 2022 10:52:25 +0100	[thread overview]
Message-ID: <87y1r69x2e.fsf@gmx.de> (raw)
In-Reply-To: <83h6xuihgc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Dec 2022 10:04:51 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli & Paul,

>> These patches address the issues raised by Michael by passing only
>> single arguments to make-directory handlers. That way, we don't need to
>> worry about whether the handlers follow the new convention. At our
>> leisure, perhaps in Emacs 30, we can upgrade the make-directory handlers
>> to support the new convention.
>
> Michael, are you okay with this? do you see any problems, real or
> potential, that could endanger the release of Emacs 29?

I've reviewed them, and in general it looks OK. Needs some testing, of
course.

Since file name handlers still raise an error in case DIR exists and
PARENTS is nil, we might see surprises in code assuming the new
behavior. I guess I'll add a change in tramp-*-handle-make-directory
like

--8<---------------cut here---------------start------------->8---
    (if (and (null parents) (file-exists-p dir))
	(if (>= emacs-major-version 29)
            t
	  (tramp-error v 'file-already-exists dir)))
--8<---------------cut here---------------end--------------->8---

And, of course, the return value (nil or t) must be added. But this
doesn't break compatibility, because until now no return value is
specified.

Similar changes to ange-ftp-make-directory.

tramp-test13-make-directory of tramp-tests.el must be adapted as well,
but this is minor. Will do.

These changes must be applied anyway, for Tramp's compatibility over
several Emacs versions.

In short, I guess we could add the patch to the emacs-29 branch.

Best regards, Michael.





  reply	other threads:[~2022-12-17  9:52 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 [this message]
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
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

  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=87y1r69x2e.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=58919@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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 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).