From: Matt M <mmerino@outlook.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "46972@debbugs.gnu.org" <46972@debbugs.gnu.org>,
"akrl@sdf.org" <akrl@sdf.org>
Subject: bug#46972: RE : RE : RE : RE : RE : bug#46972: 28.0.50; [feature/native-comp] Emacs locks itself during native compilation because of permission denied
Date: Fri, 12 Mar 2021 12:53:58 +0000 [thread overview]
Message-ID: <DB6P190MB03273F8854614F60E54EA816D66F9@DB6P190MB0327.EURP190.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <83eegklev9.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1033 bytes --]
;; oldfile maybe recreated by another Emacs in
;; between the following two rename-file calls
I don’t know what code but the comment says that it can be. This
seems to be unique to Windows for some reason but I don’t know why.
De : Eli Zaretskii <eliz@gnu.org>
Envoyé : Friday, March 12, 2021 1:45:46 PM
À : Matt M <mmerino@outlook.fr>
Cc : akrl@sdf.org <akrl@sdf.org>; 46972@debbugs.gnu.org <46972@debbugs.gnu.org>
Objet : Re: RE : RE : RE : RE : bug#46972: 28.0.50; [feature/native-comp] Emacs locks itself during native compilation because of permission denied
> From: Matt M <mmerino@outlook.fr>
> CC: "akrl@sdf.org" <akrl@sdf.org>, "46972@debbugs.gnu.org"
> <46972@debbugs.gnu.org>
> Date: Fri, 12 Mar 2021 11:37:22 +0000
>
> If I understand correctly, this is what happens currently :
>
> 1 Rename oldfile to new temporary name
> 2 Rename newfile to oldfile
> 3 If rename in 2) failed because oldfile has been recreated, go back to 1)
Why would oldfile be recreated? which code recreates it?
[-- Attachment #1.2: Type: text/html, Size: 3013 bytes --]
[-- Attachment #2: F038E641A1254CD3B029465A8B580B79.png --]
[-- Type: image/png, Size: 144 bytes --]
next prev parent reply other threads:[~2021-03-12 12:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 17:23 bug#46972: 28.0.50; [feature/native-comp] Emacs locks itself during native compilation because of permission denied Matt M
2021-03-06 18:34 ` Eli Zaretskii
2021-03-06 18:52 ` bug#46972: RE : " Matt M
2021-03-06 19:01 ` Eli Zaretskii
2021-03-06 19:02 ` bug#46972: RE : " Matt M
2021-03-06 20:03 ` Eli Zaretskii
2021-03-06 20:14 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-06 20:16 ` Eli Zaretskii
2021-03-12 0:26 ` bug#46972: RE : " Matt M
2021-03-12 7:36 ` Eli Zaretskii
2021-03-12 11:37 ` bug#46972: RE : " Matt M
2021-03-12 12:45 ` Eli Zaretskii
2021-03-12 12:53 ` Matt M [this message]
2021-03-14 10:51 ` Eli Zaretskii
2021-03-14 13:39 ` Eli Zaretskii
2021-03-14 14:07 ` bug#46972: RE : " Matt M
2021-03-14 14:24 ` 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=DB6P190MB03273F8854614F60E54EA816D66F9@DB6P190MB0327.EURP190.PROD.OUTLOOK.COM \
--to=mmerino@outlook.fr \
--cc=46972@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
/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).