unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 10257@debbugs.gnu.org, jari <jari.aalto@cante.net>
Subject: bug#10257: 23.3.1 Cygwin: network drives - file is write protected (false positive)
Date: Tue, 13 Dec 2011 15:16:41 -0500	[thread overview]
Message-ID: <4EE7B2A9.6060308@cornell.edu> (raw)
In-Reply-To: <jwviplke0j1.fsf-monnier+emacs@gnu.org>

On 12/13/2011 2:27 PM, Stefan Monnier wrote:
>> I have a question about the emacs side of this.  I wonder what the rationale
>> is for testing writability before trying to save the file, and then asking
>> the user for confirmation in case the (unreliable) test for writability
>> fails (*).
>
> Can you point us to the piece of code about which you're talking?
> Ideally, show us a sample pseudo patch (even better if it compiles, even
> better if it works) showing the kind of change you have in mind.

The code I'm talking about is near the beginning of the definition of 
`basic-save-buffer-2' in files.el:

     (if (not (file-writable-p buffer-file-name))
	(let ((dir (file-name-directory buffer-file-name)))
	  (if (not (file-directory-p dir))
	      (if (file-exists-p dir)
		  (error "%s is not a directory" dir)
		(error "%s: no such directory" dir))
	    (if (not (file-exists-p buffer-file-name))
		(error "Directory %s write-protected" dir)
	      (if (yes-or-no-p
		   (format
		    "File %s is write-protected; try to save anyway? "
		    (file-name-nondirectory
		     buffer-file-name)))
		  (setq tempsetmodes t)
		(error "Attempt to save to a file which you aren't allowed to write"))))))

I'm not (yet) proposing a change.  I'm simply asking what the rationale 
is for calling `yes-or-no-p' and making the user confirm that s/he wants 
to try to save the file.  I don't see that any harm would come from just 
trying to do what the user asked for, without making him/her ask a 
second time.  If the file really is write-protected, there will be an error.

If you agree, then I guess I would propose the following patch (not yet 
tested):

=== modified file 'lisp/files.el'
--- lisp/files.el       2011-12-04 08:02:42 +0000
+++ lisp/files.el       2011-12-13 20:08:55 +0000
@@ -4456,13 +4456,7 @@
                 (error "%s: no such directory" dir))
             (if (not (file-exists-p buffer-file-name))
                 (error "Directory %s write-protected" dir)
-             (if (yes-or-no-p
-                  (format
-                   "File %s is write-protected; try to save anyway? "
-                   (file-name-nondirectory
-                    buffer-file-name)))
-                 (setq tempsetmodes t)
-               (error "Attempt to save to a file which you aren't 
allowed to write"))))))
+             (setq tempsetmodes t)))))
      (or buffer-backed-up
         (setq setmodes (backup-buffer)))
      (let* ((dir (file-name-directory buffer-file-name))


Ken





  reply	other threads:[~2011-12-13 20:16 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 18:23 bug#10257: 23.3.1 Cygwin: network drives - file is write protected (false positive) Jari Aalto
2011-12-09 20:33 ` Ken Brown
2011-12-10  9:58   ` jaalto
2011-12-13 12:18     ` Ken Brown
2011-12-13 14:00       ` jari
2011-12-13 14:43         ` Eli Zaretskii
2011-12-13 15:12           ` Ken Brown
2011-12-13 19:27             ` Stefan Monnier
2011-12-13 20:16               ` Ken Brown [this message]
2011-12-14  2:54                 ` Stefan Monnier
2011-12-14  3:27                   ` Ken Brown
2011-12-14  8:01                     ` Jari Aalto
2011-12-14  8:35                       ` Eli Zaretskii
2011-12-14 12:24                         ` Ken Brown
2011-12-14 12:55                           ` Ken Brown
2011-12-14 13:10                             ` Eli Zaretskii
2011-12-14 14:19                               ` Ken Brown
2011-12-14 14:47                                 ` jari
2011-12-14 17:30                                 ` Eli Zaretskii
2011-12-14 17:57                                   ` Ken Brown
2011-12-15  2:43                                     ` Ken Brown
2011-12-15  2:53                                       ` Ken Brown
2011-12-15  3:19                                         ` Ken Brown
2011-12-15  4:04                                       ` Eli Zaretskii
2011-12-15 14:42                                         ` Ken Brown
2011-12-16 19:37                                           ` Ken Brown
2011-12-16 19:46                                             ` Eli Zaretskii
2011-12-16 23:15                                             ` Stefan Monnier
2011-12-17 17:08                                               ` Ken Brown
2011-12-14 14:15                             ` jari
2011-12-14 14:29                               ` Ken Brown
2011-12-14 14:43                                 ` jari
2011-12-14 17:21                                 ` Eli Zaretskii
2011-12-14 17:23             ` Richard Stallman
2011-12-13 16:26           ` jari
2011-12-13 16:52             ` Ken Brown
2011-12-13 17:48               ` jari
2011-12-13 17:48             ` Eli Zaretskii
2011-12-13 18:05               ` jari
2011-12-13 18:36                 ` Eli Zaretskii
2011-12-15 14:44           ` Jason Rumney

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=4EE7B2A9.6060308@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=10257@debbugs.gnu.org \
    --cc=jari.aalto@cante.net \
    --cc=monnier@iro.umontreal.ca \
    /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).