From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Nicolas =?UTF-8?Q?B=C3=A9rtolo?= Newsgroups: gmane.emacs.bugs Subject: bug#41242: Port feature/native-comp to Windows Date: Thu, 14 May 2020 17:16:05 -0300 Message-ID: References: <834ksi60zn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="40981"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 41242@debbugs.gnu.org To: Andrea Corallo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu May 14 22:18:31 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 1jZKJL-000AXS-8y for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 14 May 2020 22:18:31 +0200 Original-Received: from localhost ([::1]:37830 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jZKJK-00040h-7z for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 14 May 2020 16:18:30 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37540) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jZKHu-0001US-P2 for bug-gnu-emacs@gnu.org; Thu, 14 May 2020 16:17:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51700) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jZKHu-0003TS-Fz for bug-gnu-emacs@gnu.org; Thu, 14 May 2020 16:17:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jZKHu-0003QH-CX for bug-gnu-emacs@gnu.org; Thu, 14 May 2020 16:17:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Nicolas =?UTF-8?Q?B=C3=A9rtolo?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 14 May 2020 20:17:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 41242 X-GNU-PR-Package: emacs Original-Received: via spool by 41242-submit@debbugs.gnu.org id=B41242.158948739013112 (code B ref 41242); Thu, 14 May 2020 20:17:02 +0000 Original-Received: (at 41242) by debbugs.gnu.org; 14 May 2020 20:16:30 +0000 Original-Received: from localhost ([127.0.0.1]:35013 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jZKHN-0003PL-UX for submit@debbugs.gnu.org; Thu, 14 May 2020 16:16:30 -0400 Original-Received: from mail-ot1-f42.google.com ([209.85.210.42]:44734) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jZKHH-0003N5-B6 for 41242@debbugs.gnu.org; Thu, 14 May 2020 16:16:23 -0400 Original-Received: by mail-ot1-f42.google.com with SMTP id j4so73632otr.11 for <41242@debbugs.gnu.org>; Thu, 14 May 2020 13:16:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=9Vx55hgaR3yrZ9Jj/ALL0PDDeXgP6/vID2ufUe7VjYs=; b=Suup2cWSNnM5gY7v5lDderKOVsfyBLJqn1heYs78kf82nQxW58t5veXZK1z7GvKls2 s2s4k6owl13otyutcEz+Wp/7Y0cKSzFBHNKg2dGATf5ffytLfHpAT+Ti1S09VsTPvhlU HCWrS8sfLzyMH4QD86IsJmmDwrUqdWvO5GUbp5OYyD6YiMH3ULsX/8XhimVSxVcXnZRe TohYzfUN+ETDk/6FdMw8z2DpYOpa52Vr7xdD8xLFqLXHGiUPINFThAInpq5bwqBGoRKh X2JiJltNSSpwfg0OJB1f5VlYoiUrjNRgA1KWKCtBKb/wQ8hvzeVxA7Amhu3SXs41PsCX 0I5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9Vx55hgaR3yrZ9Jj/ALL0PDDeXgP6/vID2ufUe7VjYs=; b=RoqYaDMBF6Ic2647YiJJG5mZ1QEkY04ZDNskPfuGw2AS4ITd8K0KOR+le2Htenu5ZM JJkIrQ3wSobIO062wHyJwnQxtpT2i5e1paQemUQy9alqG7h4v4tL5FgHzAEX4d5IIVIO +VykCzVzH+S1oWRM8iyA+pcIqc2TY7/M6rhtpMsmweb2r5BL6SsIsTDZIME5KbnvTmIv FaLzvw6WeTMyy2tN6hGyYX5QXo0TDf6xSY9Gb9aF0v7Eth3o3Kw3QjIZugaubR+TP/Wm IySxY3fD3XD1Mzsq0yQHve8Wjy2wAl3dX+CGapKR4C4lNLcGTqtV7gZoSrje1NwqJc+q w3QQ== X-Gm-Message-State: AOAM530GAx34CdAwUCQnjUyV7luPhqb1w3uN2iZTJXr2oBkV93oDZ6XR 4sBlRjOtfcR7VuvmN/0hka/LWtrfH/bhOmoU+0c= X-Google-Smtp-Source: ABdhPJwRRRntHQzwR7YqpYScpVQdmva5T0NYogH7+NZIcHbeQtPiYalKG48Nc5EQL3irE+Yo37JyBozOgWl7p19sADo= X-Received: by 2002:a9d:5f09:: with SMTP id f9mr4922214oti.202.1589487377519; Thu, 14 May 2020 13:16:17 -0700 (PDT) In-Reply-To: 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:180267 Archived-At: > Yes, but I think we could say: the last Emacs closing that used any file > that was (at a certain point in life) foo.eln removes all the old > foo.eln.* I think this would work :). We could even remove the pid file. Just do the equivalent of `rm $ELN.old*` after FreeLibrary(). If the deletion fails then that means that another Ema= cs has loaded that file. It would take of files left over from crashes too. We would need to change `package-delete` though. It would no longer fully delete the directory. Maybe other functions in `package.el` would need to be updated to deal with these changes. Nicolas. El jue., 14 may. 2020 a las 16:58, Andrea Corallo () escribi= =C3=B3: > > Nicolas B=C3=A9rtolo writes: > > >> As you said the problem is to decide who has the duty to remove the fi= le > >> at last. If each Emacs deposes a file says .foo.eln-pidxxx for the > >> whole time is using foo.eln should be easy for the last Emacs to > >> understand it is really the last and has to do the clean-up in the cas= e > >> foo.eln was renamed in foo.eln*whatever > > > > That file would be create when opening foo.eln, but when > > Emacs is closing we don't know what file it refers to: > > - foo.eln > > - foo.eln.old > > - foo.eln.old2 > > - foo.eln.oldN > > > > These last files could be created if foo.eln.old exists at the time of = renaming. > > Yes, but I think we could say: the last Emacs closing that used any file > that was (at a certain point in life) foo.eln removes all the old > foo.eln.* > > If is the last using any of the foo.eln* it can do that safely no? > > -- > akrl@sdf.org