From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.bugs Subject: bug#27986: 26.0.50; 'rename-file' can rename files without confirmation Date: Mon, 11 Sep 2017 10:25:25 -0700 Organization: UCLA Computer Science Department Message-ID: <0db4d790-81de-de02-074b-71308d729d2d@cs.ucla.edu> References: <61980dde-3d68-7200-e7f4-98f62e410060@cs.ucla.edu> <1002ee73-0ab5-409b-831f-0c283c322264@cs.ucla.edu> <83o9rignt6.fsf@gnu.org> <83d17whl72.fsf@gnu.org> <8e6de468-600c-4f2d-a21a-c2ff3a63d065@cs.ucla.edu> <83zib0g221.fsf@gnu.org> <2bb4b7ee-6bf9-df3d-5cd8-ae7992b9f2e7@cs.ucla.edu> <83wp64fdc4.fsf@gnu.org> <83valnfv9u.fsf@gnu.org> <7f0c12f6-57eb-63b9-c296-e062cbf0710c@cs.ucla.edu> <83o9rffqfp.fsf@gnu.org> <83efsbfmij.fsf@gnu.org> <83efs8dp4b.fsf@gnu.org> <2ff8e814-b75d-1c9f-a096-8ad644c01ccc@cs.ucla.edu> <8360cpthq9.fsf@gnu.org> <83efrdrwkj.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1505153160 10302 195.159.176.226 (11 Sep 2017 18:06:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 11 Sep 2017 18:06:00 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 Cc: rms@gnu.org, johnw@gnu.org, p.stephani2@gmail.com, michael.albinus@gmx.de, monnier@IRO.UMontreal.CA, 27986@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Sep 11 20:05:50 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1drT5N-0001EL-Fq for geb-bug-gnu-emacs@m.gmane.org; Mon, 11 Sep 2017 20:05:29 +0200 Original-Received: from localhost ([::1]:59589 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drT5S-0006on-Iw for geb-bug-gnu-emacs@m.gmane.org; Mon, 11 Sep 2017 14:05:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1drSTF-0003Tg-6A for bug-gnu-emacs@gnu.org; Mon, 11 Sep 2017 13:26:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1drSTC-0003eU-1h for bug-gnu-emacs@gnu.org; Mon, 11 Sep 2017 13:26:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:53473) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1drSTB-0003eN-UH for bug-gnu-emacs@gnu.org; Mon, 11 Sep 2017 13:26:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1drSTB-0000jx-Me for bug-gnu-emacs@gnu.org; Mon, 11 Sep 2017 13:26:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Paul Eggert Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 11 Sep 2017 17:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 27986 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: security Original-Received: via spool by 27986-submit@debbugs.gnu.org id=B27986.15051507342811 (code B ref 27986); Mon, 11 Sep 2017 17:26:01 +0000 Original-Received: (at 27986) by debbugs.gnu.org; 11 Sep 2017 17:25:34 +0000 Original-Received: from localhost ([127.0.0.1]:33921 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1drSSk-0000jH-E1 for submit@debbugs.gnu.org; Mon, 11 Sep 2017 13:25:34 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:45294) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1drSSi-0000j5-VE for 27986@debbugs.gnu.org; Mon, 11 Sep 2017 13:25:33 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 4F29E160CE7; Mon, 11 Sep 2017 10:25:26 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id e1ZcO4muKrBb; Mon, 11 Sep 2017 10:25:25 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 88231160CEA; Mon, 11 Sep 2017 10:25:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DEb7_ATJnSGX; Mon, 11 Sep 2017 10:25:25 -0700 (PDT) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 66EA01600DE; Mon, 11 Sep 2017 10:25:25 -0700 (PDT) In-Reply-To: <83efrdrwkj.fsf@gnu.org> Content-Language: en-US X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:136800 Archived-At: On 09/11/2017 10:09 AM, Eli Zaretskii wrote: > I think there was a confusion here between interactive and > non-interactive uses of rename-file. For interactive use, AFAIR we > agreed that the behavior should stay as before, in particular to be > consistent with e.g. invocation of 'mv' from the shell prompt. That wasn't my understanding, and the email record is consistent with my interpretation. Although we discussed mv, the last comment on that topic was from John, who wrote about mv that "Making the Emacs version more restrictive, however, makes sense" (Bug#27986#145). This corresponds to the patch I installed, whose rename-file is more restrictive than mv because it balks at renaming a regular file F to G when G is not a directory name but happens to be an existing directory. As I wrote, I don't think this will matter much in practice because the point is moot when file name completion is used. If I'm wrong and it is a significant problem, I can still implement the suggestion in Bug#27986#97 to ameliorate it. It may be better, though, to try out what we have now for a while, to see whether that suggestion would actually help.