From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Angelo Graziosi Newsgroups: gmane.emacs.devel Subject: Re: How to stop desktop.lock file creation Date: Sat, 26 Mar 2022 22:30:00 +0100 (CET) Message-ID: <1611306500.320421.1648330200906@mail1.libero.it> References: <1843424395.177680.1648161239137@mail1.libero.it> <838rsyczh6.fsf@gnu.org> <1960767723.287175.1648248799870@mail1.libero.it> <83ils1b6x2.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29208"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 26 22:31:22 2022 Return-path: Envelope-to: ged-emacs-devel@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 1nYE0I-0007Sz-5U for ged-emacs-devel@m.gmane-mx.org; Sat, 26 Mar 2022 22:31:22 +0100 Original-Received: from localhost ([::1]:54230 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nYE0H-0001oP-2d for ged-emacs-devel@m.gmane-mx.org; Sat, 26 Mar 2022 17:31:21 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:55720) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYDz3-00011i-6V for emacs-devel@gnu.org; Sat, 26 Mar 2022 17:30:05 -0400 Original-Received: from smtp-31-i2.italiaonline.it ([213.209.12.31]:50594 helo=libero.it) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nYDz1-0007qy-8p for emacs-devel@gnu.org; Sat, 26 Mar 2022 17:30:04 -0400 Original-Received: from oxapps-32-144.iol.local ([10.101.8.190]) by smtp-31.iol.local with ESMTPA id YDyynZylHsXp4YDyynQbWc; Sat, 26 Mar 2022 22:30:01 +0100 x-libjamoibt: 1601 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=libero.it; s=s2021; t=1648330201; bh=VfTLQrTRant954hwO7V5AlVXy4kgj5MbkBhyks0u4KM=; h=From; b=P198irxcGMuD6iel3PdRJCb+MhnQe6fCujzBVvtfAtE4hllV1BDragfeiAz4MNgr4 aXdKbe6F9QrBoCYsRScfPznh9WImpVPqlJmmJk5/fusqjfjQQNaOZ93JUyDlk+sV1Z clPGRLFx1Cbt0651P7++dsrsQgVMaVNXO/16andnGY6NyJ4jZEJvuUD6XSVnwDtDdU 1mSwef1bsSCh33WD3EZWYImrjFMx59LssbV+qYr8uTt8Od8VD34zezm1l2Pa5PVMtO kBLGWdWmJXXLY/xgGU6iGwwr26vzTew3QojtjB2uCrXUfgdaExFFLJWZ0Xcdhfqbdn pATuS/AyfOqOA== X-CNFS-Analysis: v=2.4 cv=HLMGqqhv c=1 sm=1 tr=0 ts=623f85d9 cx=a_exe a=+LyvvGPX93CApvOVpnXrdQ==:117 a=zlL5DDtatYgA:10 a=IkcTkHD0fZMA:10 a=1pep0PMDP0kA:10 a=mDV3o1hIAAAA:8 a=EbmIWUBdEPoxzc__4zMA:9 a=QEXdDO2ut3YA:10 a=_FVE-zBwftR9WsbkzFJk:22 In-Reply-To: <83ils1b6x2.fsf@gnu.org> X-Priority: 3 Importance: Normal X-Mailer: Open-Xchange Mailer v7.10.5-Rev39 X-Originating-IP: 79.13.231.87 X-Originating-Client: open-xchange-appsuite x-libjamsun: Sn8yaS1Q4KT4at+cSb7sEhwWBofhY2w2 x-libjamv: 2IysjDeCKlM= X-CMAE-Envelope: MS4xfJRPceW1NIYT+MW1G41JOLUrJYkgdL259z+9fcmytlALABmbck+2/DuVKzNVHF8yg7QgLWaGI5WQ/ykSK9FH6rk3y9CivdYEUFmY2fl54gnuA2DfK7bT XknBA5li74nmXDUtDtZ2Em69jG0AsoeCAdx6CBMr3hXYPcBac5CYd1DsS46akkLJh8LuD/jne+MRJ0GYusof0HpIJvqyBrbdhYLUnbWVRPldf1WWUS/PWiAm Received-SPF: pass client-ip=213.209.12.31; envelope-from=angelo.g0@libero.it; helo=libero.it X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:287492 Archived-At: > Il 26/03/2022 06:48 Eli Zaretskii ha scritto: > > > > Date: Fri, 25 Mar 2022 23:53:19 +0100 (CET) > > From: Angelo Graziosi > > Cc: emacs-devel@gnu.org > > > > > Why do you need to delete the desktop lock file? If you are annoyed > > > > The alternative is to accept to load it or not but why should i play this game.. > > You don't need to play this game. If you set > desktop-load-locked-desktop to t, Emacs will unconditionally load the > desktop even if locked, no questions asked. Its effect is the same as > not having the lock at all, when the process which locked the desktop > no longer runs. When Emacs ask for loading the desktop file it says "Warning: desktop file appears to be in use by PID xyza. Using it may cause conflicts. Use it anyway? (y or n)" So, _if it says that could be conflicts_, in my opinion, the best way to go is to accept it, close Emacs, restart Emacs, so that it starts in a clean state. Why I have to to all this? Really I need this? or should I accept with the risk of conflicts (i am sure they do not occur!)? > > > > by the question Emacs asks when you invoke it the next time, you can > > > simply customize desktop-load-locked-desktop to the value t, then it > > > will not ask any questions. Yes, I could do that, but implicitly accepting the risk of conflicts (I am sure they do not occur!) In all this, It seems I have to do a sterile work. > > > Emacs worked the same before its introduction... > > The lock was introduced in Emacs 22.2, quite some time ago. It isn't > a new feature. I know this and it is what I did mean. If users could live without the lock file until version 22 why can't they live without it with the current version? In short: really we need this lock file? really it is useful in all situations? Why not adding a flag to avoid its creation and that the user sets at its own risk? Yes, setting desktop-load-locked-desktop to the value t is something similar to what I am asking but not exactly the equivalent. In any case, thanks for all clarifications.