From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: djc Newsgroups: gmane.emacs.help Subject: Re: {file} "locked by ... pid NNN", but there is no process NNN Date: Tue, 19 Jan 2016 02:40:21 -0800 (PST) Message-ID: References: <2a0feba2-1cf6-498f-bbea-7fca8ce5d56e@googlegroups.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1453200335 31523 80.91.229.3 (19 Jan 2016 10:45:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Jan 2016 10:45:35 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Jan 19 11:45:33 2016 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aLTn1-00052p-No for geh-help-gnu-emacs@m.gmane.org; Tue, 19 Jan 2016 11:45:31 +0100 Original-Received: from localhost ([::1]:36157 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLTn0-0001yg-TK for geh-help-gnu-emacs@m.gmane.org; Tue, 19 Jan 2016 05:45:30 -0500 X-Received: by 10.50.141.129 with SMTP id ro1mr16964248igb.12.1453200022323; Tue, 19 Jan 2016 02:40:22 -0800 (PST) X-Received: by 10.50.3.73 with SMTP id a9mr295532iga.4.1453200022307; Tue, 19 Jan 2016 02:40:22 -0800 (PST) Original-Path: usenet.stanford.edu!h5no6621695igh.0!news-out.google.com!l1ni699igd.0!nntp.google.com!h5no6621686igh.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help In-Reply-To: <2a0feba2-1cf6-498f-bbea-7fca8ce5d56e@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=185.110.72.137; posting-account=W7YkKQoAAACBK5oRU_iH-VD6YfJuNxe9 Original-NNTP-Posting-Host: 185.110.72.137 User-Agent: G2/1.0 Injection-Date: Tue, 19 Jan 2016 10:40:22 +0000 Original-Xref: usenet.stanford.edu gnu.emacs.help:216484 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:108775 Archived-At: The situation was too complex and too intermittent to simplify easily for d= iagnosis, but I think I know generally what's happening: emacs is failing t= o delete its own lock of a file that I was working on once, but either (1) = whose buffer has been killed or (2) where the lock has survived exiting and= re-opening emacs. On Windows, emacs also doesn't necessarily release Windows handles of files= and directories for which it no longer has any associated buffer. I've se= en this repeatedly. djc