From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.help Subject: Re: emacsclient uses obsolete "server" file on Windows Date: Thu, 12 Jun 2008 16:33:11 +0200 Message-ID: References: <484ACDD0.80209@resiak.org> <484BFAE3.1000105@resiak.org> <4850E139.6060105@resiak.org> <48512949.5020104@gmail.com> <48512F95.8000108@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1213281325 4274 80.91.229.12 (12 Jun 2008 14:35:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 12 Jun 2008 14:35:25 +0000 (UTC) Cc: help-gnu-emacs@gnu.org, djc To: "Lennart Borgman (gmail)" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Jun 12 16:36:05 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K6nsn-0003sm-Ux for geh-help-gnu-emacs@m.gmane.org; Thu, 12 Jun 2008 16:34:34 +0200 Original-Received: from localhost ([127.0.0.1]:43164 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6ns0-0004c5-4h for geh-help-gnu-emacs@m.gmane.org; Thu, 12 Jun 2008 10:33:44 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K6nrW-0004Vn-Su for help-gnu-emacs@gnu.org; Thu, 12 Jun 2008 10:33:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6nrV-0004Tz-B0 for help-gnu-emacs@gnu.org; Thu, 12 Jun 2008 10:33:14 -0400 Original-Received: from [199.232.76.173] (port=45161 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6nrU-0004Ts-Ql for help-gnu-emacs@gnu.org; Thu, 12 Jun 2008 10:33:12 -0400 Original-Received: from wa-out-1112.google.com ([209.85.146.182]:58800) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K6nrU-0007PJ-F0 for help-gnu-emacs@gnu.org; Thu, 12 Jun 2008 10:33:12 -0400 Original-Received: by wa-out-1112.google.com with SMTP id m34so2942688wag.10 for ; Thu, 12 Jun 2008 07:33:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=XPFxwucn0J3eYCkPRmL5FfNEillbp61RNv5/dWnG3Zo=; b=Hu6iMhQPSGlQ6/jz8LXsr4+cW5J7ntTF+lnQbmMshYSpWgTgaWJZJLwA+rIFKnyROL Q8D203MqGEmJ8vmB400oxPQ69L5ZygSA8EHetfVmLhRxjeixF7+g3ZTzpyCN2KJBKbfK 3shabMu3LMc8tuVWd6MHyVqZv0EU4WQ4HrUho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=JdlL5biUUaB3Zu8XGeQg/jwDfLhUd9ROmn1n05WrLAyNrxBsYw18IdiL3WdvnbuwBW HxTUURZjr509iHTIwrJGg6KiPUaBpSKF5IlQfiwutFtVb1mzV8E08KISy7vDilJCMDCB pNZ8EvbbGrqx1pVztBu7cuijyHicqxGrYRh+A= Original-Received: by 10.114.201.1 with SMTP id y1mr1574016waf.93.1213281191419; Thu, 12 Jun 2008 07:33:11 -0700 (PDT) Original-Received: by 10.114.167.12 with HTTP; Thu, 12 Jun 2008 07:33:11 -0700 (PDT) In-Reply-To: <48512F95.8000108@gmail.com> Content-Disposition: inline X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:54765 Archived-At: On Thu, Jun 12, 2008 at 16:15, Lennart Borgman (gmail) wrote: > Are all writing process on the same machine Not necesarily. > so that a simple semaphore can be used? A "simple semaphore" cannot be used from elisp. Locking the file (with lock-buffer, though that does not work on Windows) would be possible. IIRC, Stefan (who wrote that comment) didn't want the second Emacs instance to get an error while trying to write the file. But, truth be told, I don't remember the issues well and I could be misrepresenting his intention. I suggest you take a look at the emacs-devel archives, a few months before 22.1 was released. Juanma