From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Evil Boris Newsgroups: gmane.emacs.devel Subject: RMAIL file locking problem? Date: Tue, 19 Apr 2005 12:16:41 -0400 Message-ID: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1113929129 15698 80.91.229.2 (19 Apr 2005 16:45:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 19 Apr 2005 16:45:29 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Apr 19 18:45:25 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DNvpB-0005Zs-0Z for ged-emacs-devel@m.gmane.org; Tue, 19 Apr 2005 18:43:45 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DNvtW-0003JO-2v for ged-emacs-devel@m.gmane.org; Tue, 19 Apr 2005 12:48:14 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DNvqx-0002GV-Ox for emacs-devel@gnu.org; Tue, 19 Apr 2005 12:45:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DNvqv-0002FY-Pj for emacs-devel@gnu.org; Tue, 19 Apr 2005 12:45:34 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DNvqt-0001n0-H3 for emacs-devel@gnu.org; Tue, 19 Apr 2005 12:45:33 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1DNvSv-0002Kz-QX for emacs-devel@gnu.org; Tue, 19 Apr 2005 12:20:46 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DNvLx-0000AK-QI for emacs-devel@gnu.org; Tue, 19 Apr 2005 18:13:33 +0200 Original-Received: from 207-38-193-43.c3-0.wsd-ubr1.qens-wsd.ny.cable.rcn.com ([207.38.193.43]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2005 18:13:33 +0200 Original-Received: from evilborisnet by 207-38-193-43.c3-0.wsd-ubr1.qens-wsd.ny.cable.rcn.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 19 Apr 2005 18:13:33 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 28 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 207-38-193-43.c3-0.wsd-ubr1.qens-wsd.ny.cable.rcn.com User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (windows-nt) Cancel-Lock: sha1:WeTJzcuGhJDxwAAj4WZQedR0LOs= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:36115 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:36115 I use rmail to read mail. I noticed that starting sometime after the summer, rmail would lock the mail file (i.e., ~/RMAIL) even if it did not _seem_ modified (I have no way of knowing if it actually is modified). More precisely, here's the behavior I observe: I type "s" in rmail. It saves the file. I do it again. It says "no changes need to be saved". I check that ~/RMAIL is not locked. Some time later, __with no actions on my part__, I notice that ~/RMAIL is locked (i.e., the ~/.#RMAIL symbolic link appears). If I go back to Emacs and type "s" in rmail, it says "no changes need to be saved"! I can __force__ a save by typing "t" and "t". But that's silly, of course... Versions: current CVS, updated reasonably frequently. Sun/Solaris 2.7. Noticed this sometime after last summer. Why it bothers me: I often have several copies of Emacs running simultaneously, one on the X display at work, one on ssh/terminal from home or in screen/terminal. I switch between the two and would like to be able to read mail in both (not concurrently, of course). Rmail locking the files makes me have to jump through hoops to get one copy to unlock the file so I can use it from the other. Any and all ideas would be appreciated. I tried this with "emacs -Q" and seemed to do the same, btw. --Boris