unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Takaaki.Ota@am.sony.com
Cc: 22795@debbugs.gnu.org
Subject: bug#22795: 25.0.91; Can't write read only file on w32
Date: Sat, 14 May 2016 12:17:03 +0300	[thread overview]
Message-ID: <83wpmx6ltc.fsf@gnu.org> (raw)
In-Reply-To: <83oaay6u4o.fsf@gnu.org> (message from Eli Zaretskii on Tue, 01 Mar 2016 18:27:35 +0200)

> Date: Tue, 01 Mar 2016 18:27:35 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 22795@debbugs.gnu.org
> 
> > Date: Mon, 29 Feb 2016 13:34:36 -0800
> > CC: <22795@debbugs.gnu.org>
> > From: "Ota, Takaaki" <Takaaki.Ota@am.sony.com>
> > 
> > I just tried again with "run -Q" from gdb and the result is the same.
> > 24.5 never called sys_rename() and 25.0.91 called sys_rename() with
> > two same names.
> 
> What about Frename_file? does 24.5 call it in this scenario?
> 
> If it doesn't, then please look at the beginning of backup-buffer (in
> files.el), make sure it is called in 24.5 in this scenario, and then
> please tell what are the values of real-file-name and backup-info in
> this part at the beginning of backup-buffer:
> 
> 	(let* ((real-file-name (file-chase-links buffer-file-name))
> 	       (backup-info (find-backup-file-name real-file-name)))
> 
> Also, what are the values of make-backup-files, backup-inhibited, and
> buffer-backed-up in the buffer that visits the read-only file?
> 
> Btw, is that file under some kind of version control, per chance?
> 
> And please make sure, from now on, to test everything in "emacs -Q",
> to prevent any customizations from getting in the way of this
> investigation.

Ping!  Can we please continue this investigation?

If the problem is no longer reproducible with the latest pretest
25.0.9x, or if you can no longer afford looking into this, I will most
probably close the bug.

Thanks.





  reply	other threads:[~2016-05-14  9:17 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 16:44 bug#22795: 25.0.91; Can't write read only file on w32 Ota, Takaaki
2016-02-24 19:09 ` Eli Zaretskii
2016-02-24 21:57   ` Ota, Takaaki
2016-02-25 16:47     ` Eli Zaretskii
2016-02-25 17:08       ` Ota, Takaaki
2016-02-25 17:12         ` Ota, Takaaki
2016-02-25 18:09         ` Eli Zaretskii
2016-02-25 18:15           ` Ota, Takaaki
2016-02-26 19:26           ` Ota, Takaaki
2016-02-26 21:53             ` Eli Zaretskii
2016-02-29 16:40               ` Ota, Takaaki
2016-02-29 17:13                 ` Eli Zaretskii
2016-02-29 17:39                   ` Ota, Takaaki
2016-02-29 17:53                   ` Ota, Takaaki
2016-02-29 18:05                     ` Ota, Takaaki
2016-02-29 18:48                       ` Eli Zaretskii
2016-02-29 19:28                         ` Ota, Takaaki
2016-02-29 20:06                           ` Eli Zaretskii
2016-02-29 21:34                             ` Ota, Takaaki
2016-03-01 16:27                               ` Eli Zaretskii
2016-05-14  9:17                                 ` Eli Zaretskii [this message]
2016-05-19 18:47                                   ` Ota, Takaaki
2016-05-19 19:47                                     ` Eli Zaretskii
2016-05-25 16:55                                   ` Eli Zaretskii
2016-06-01 17:22                                     ` Ota, Takaaki
2016-06-04  9:01                                       ` Eli Zaretskii
2016-06-06 16:24                                         ` Ota, Takaaki
2016-06-06 19:10                                           ` Eli Zaretskii
2016-06-06 20:46                                             ` Ota, Takaaki
2016-06-07  2:42                                               ` Eli Zaretskii
2016-06-07 23:02                                                 ` Ota, Takaaki
2016-06-08 17:07                                                   ` Eli Zaretskii
2016-12-07 21:08                                                     ` Glenn Morris
2016-02-29 18:31                     ` Eli Zaretskii

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=83wpmx6ltc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22795@debbugs.gnu.org \
    --cc=Takaaki.Ota@am.sony.com \
    /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).