From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#29412: 27.0.50; dired-toggle-read-only should (at some point!) check that the direcory is writeable Date: Sun, 13 Dec 2020 21:58:45 +0200 Organization: LINKOV.NET Message-ID: <87im95eb0j.fsf@mail.linkov.net> References: <87o9nt2cvo.fsf@ctlt579.codethink.co.uk> <87y2i35ke7.fsf@gnus.org> <505c79af-0056-4f66-aca8-9559f6ef2bff@default> <878sa2qfmq.fsf@mail.linkov.net> <5aa02c80-bcf2-4e99-915b-013275f3328d@default> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1585"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: Robert Marshall , Lars Ingebrigtsen , 29412@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Dec 13 21:05:11 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1koXcF-0000HK-Dk for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 13 Dec 2020 21:05:11 +0100 Original-Received: from localhost ([::1]:33318 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1koXcD-00051c-VI for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 13 Dec 2020 15:05:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36618) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1koXc6-00051S-MW for bug-gnu-emacs@gnu.org; Sun, 13 Dec 2020 15:05:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38849) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1koXc6-0007o9-F4 for bug-gnu-emacs@gnu.org; Sun, 13 Dec 2020 15:05:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1koXc6-0001zr-Am for bug-gnu-emacs@gnu.org; Sun, 13 Dec 2020 15:05:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 13 Dec 2020 20:05:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 29412 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: fixed Original-Received: via spool by 29412-submit@debbugs.gnu.org id=B29412.16078898957627 (code B ref 29412); Sun, 13 Dec 2020 20:05:02 +0000 Original-Received: (at 29412) by debbugs.gnu.org; 13 Dec 2020 20:04:55 +0000 Original-Received: from localhost ([127.0.0.1]:50392 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1koXbz-0001yv-K1 for submit@debbugs.gnu.org; Sun, 13 Dec 2020 15:04:55 -0500 Original-Received: from relay10.mail.gandi.net ([217.70.178.230]:47141) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1koXbx-0001y4-70 for 29412@debbugs.gnu.org; Sun, 13 Dec 2020 15:04:54 -0500 Original-Received: from mail.gandi.net (m91-129-99-98.cust.tele2.ee [91.129.99.98]) (Authenticated sender: juri@linkov.net) by relay10.mail.gandi.net (Postfix) with ESMTPSA id DC325240002; Sun, 13 Dec 2020 20:04:44 +0000 (UTC) In-Reply-To: <5aa02c80-bcf2-4e99-915b-013275f3328d@default> (Drew Adams's message of "Sun, 13 Dec 2020 08:55:36 -0800 (PST)") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:196005 Archived-At: >> Then maybe better would be to ask a y-or-n question >> whether the user still wants to edit the unwritable buffer. > > I disagree. This should be handled _exactly_ the > same way we handle a buffer for a file that is > read-only. I see no argument why we should treat > a directory buffer different from a file buffer. Asking a y-or-n question is _exactly_ what 'C-x C-q' does in wdired, i.e. after typing 'C-x C-q' (wdired-exit) it asks a question: Buffer modified; save changes? (y or n) So now entering wdired mode does the same thing with 'C-x C-q' (dired-toggle-read-only): Directory isn't writable; edit anyway? (y or n)