From: Eli Zaretskii <eliz@gnu.org>
To: Jari Aalto <jari.aalto@cante.net>
Cc: 10257@debbugs.gnu.org, jari.aalto@cante.net
Subject: bug#10257: 23.3.1 Cygwin: network drives - file is write protected (false positive)
Date: Wed, 14 Dec 2011 03:35:07 -0500 [thread overview]
Message-ID: <E1RakIt-0003NH-Lz@fencepost.gnu.org> (raw)
In-Reply-To: <87liqf1t04.fsf@picasso.cante.net> (message from Jari Aalto on Wed, 14 Dec 2011 10:01:47 +0200)
> From: Jari Aalto <jari.aalto@cante.net>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>, 10257@debbugs.gnu.org, jari <jari.aalto@cante.net>
> Date: Wed, 14 Dec 2011 10:01:47 +0200
>
> I'm proposing following,
> Jari
>
> 2011-12-14 Jari Aalto <jari.aalto@cante.net>
>
> * files.el (basic-save-buffer-2): Add
> `save-buffer-read-only-confirm-flag' to control asking to a
> write-protected file.
> (save-buffer-read-only-confirm-flag): New user variable
> (bug#10257).
Yuck! Are we going to add a knob for every possible misconfiguration
of network filesystems and/or for every incompatibility in Posix
emulation layers on Windows?
Up till now, the way to deal with this was either to change the
generic code (where it was deemed to be deficient in the first place),
or ask the maintainers of the platform to fix that either in the
platform libraries or in platform-specific code in Emacs. I think
that is the right way; adding a user option every time is not, IMNSHO.
If native Windows and even MS-DOS ports can DTRT with this, then how
come Cygwin cannot?
next prev parent reply other threads:[~2011-12-14 8:35 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
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 [this message]
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=E1RakIt-0003NH-Lz@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=10257@debbugs.gnu.org \
--cc=jari.aalto@cante.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).