From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Tramp and timers Date: Sun, 13 Dec 2020 15:55:32 -0500 Message-ID: References: <87ft4c5lfu.fsf@gmx.de> <87wnxl4knf.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21538"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 13 21:56:14 2020 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 1koYPe-0005VC-8H for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Dec 2020 21:56:14 +0100 Original-Received: from localhost ([::1]:54108 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1koYPd-00008Z-9s for ged-emacs-devel@m.gmane-mx.org; Sun, 13 Dec 2020 15:56:13 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48150) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1koYP4-00084k-LM for emacs-devel@gnu.org; Sun, 13 Dec 2020 15:55:39 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:52928) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1koYP2-0000uc-8m for emacs-devel@gnu.org; Sun, 13 Dec 2020 15:55:37 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id CCBA11002B8; Sun, 13 Dec 2020 15:55:34 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 5D554100225; Sun, 13 Dec 2020 15:55:33 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1607892933; bh=J4glDSG099ybZENIZ/d6pCbPkZNJVXfnGll90a9Mxi0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=eG0BgfhyjgNrOB6e1vfdLMnv03Rd2wxXRucOvVcL93nKesSmZYGR8qNJq5QktTePR InyFMTGmLdYN/61ucnaKpzLge0tVSLzwGPZLMjD4TSVKDDu3hNxE+SpwrR8PFlFnd7 x6WgJfRbSm/jnrZSm3kzAnca07KX7wPf/odtri0vurO/XzWYM0aOYnuHM2vrrPuZo4 dX+yl2onLFFYs4x2zTF45MUw4FBnKFNX452sSDMHGb6gRgIoX1nzJGszPl4ZRG4vBu Ekb8ZWL1PMMFT0oe+2RSESFiQuN8A6knVM3DIvoWvvUxKRgtTS5/uMiis2HwClRowu k6qNVTBHH2S2g== Original-Received: from alfajor (69-165-136-52.dsl.teksavvy.com [69.165.136.52]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 236A3120246; Sun, 13 Dec 2020 15:55:33 -0500 (EST) In-Reply-To: <87wnxl4knf.fsf@gmx.de> (Michael Albinus's message of "Sun, 13 Dec 2020 19:37:40 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:260775 Archived-At: >> Every connection should have a lock. Whenever the connection is "in >> use", we take the lock. > That's how I have implemented it. The lock is kept per (connection) > process object. Great. >> If they don't, then the risk getting `tramp-recursive-access`. > In my current implementation, I have declared a new standard error > 'remote-file-error'. I don't believe, that the term "tramp" shall be > part of the name. And I do plan to use it also for other internal error > situations, that's why it shouldn't be restricted to > "recursive-access". Either way is fine by me, but of course we can have it both ways: (define-error 'tramp-recursive-access "Oops" 'remote-file-error) -- Stefan