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: timer.el API Date: Mon, 03 Oct 2022 18:10:51 -0400 Message-ID: References: <87o7xc1qbh.fsf@web.de> <831qu8dqrx.fsf@gnu.org> <87bktbciup.fsf@web.de> <875yjfo105.fsf@web.de> <87fsii0vvp.fsf@web.de> <87zgge3vzv.fsf@web.de> <87y1vwq0su.fsf@web.de> <87ill0zkrd.fsf@web.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="33342"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Madhu , emacs-devel@gnu.org To: Michael Heerdegen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 04 00:13:14 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 1ofTgX-0008VW-Ru for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 00:13:13 +0200 Original-Received: from localhost ([::1]:39304 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofTgW-0001ym-PN for ged-emacs-devel@m.gmane-mx.org; Mon, 03 Oct 2022 18:13:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38894) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofTeO-00082H-UV for emacs-devel@gnu.org; Mon, 03 Oct 2022 18:11:00 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:61467) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofTeM-0005nQ-8j for emacs-devel@gnu.org; Mon, 03 Oct 2022 18:10:59 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id CA6ED4421BE; Mon, 3 Oct 2022 18:10:55 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 614A24421A7; Mon, 3 Oct 2022 18:10:54 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1664835054; bh=/vwyWZ9Jh6c9Zs71ZWBRi4VWIT1dQNoYTBs61G1EDaw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=cUzq4DNRcnxqZmkDssCHpDQz+PfVFwYsapcgOAEvPNioVqU+Q/VO/dfYv1u4x6Sy9 ahQiOw8mGjO8wnDpXUa17jJF+rjcMp5cC9/C937wGNOYbu8DlKjP5nm5ErSFVrAAEQ ogshbs1dscPJ/9tgowyOYrokdGpgssAU/i1qsPuDd/J2OAkpSvcAYE66QEL/9C8pKZ OnrBJSgRTF6MVvV7QP35RVATpSlYI58JPQi1Sq27TxEg0Brc6PeqTgRg0m5HncDZVN AHCSiRUXPbXg8r76ZxffQswNRY/lTyXUVJ951x1VnxT8cqhPFA2WwlAXTUV1e3arB9 m6RvOSNzXgxEA== Original-Received: from alfajor (65-110-220-202.cpe.pppoe.ca [65.110.220.202]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 301D6120DD1; Mon, 3 Oct 2022 18:10:54 -0400 (EDT) In-Reply-To: <87ill0zkrd.fsf@web.de> (Michael Heerdegen's message of "Mon, 03 Oct 2022 22:59:18 +0200") 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.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:296802 Archived-At: Michael Heerdegen [2022-10-03 22:59:18] wrote: > Stefan Monnier writes: >> And its effect is very poorly defined in its docstring. So whichever >> behavior we choose for it, I'm sure someone can come up with >> a legitimate case where that precise behavior is indeed needed. > > Madhu wrote: >> The idea was to handle a "mode" where keystrokes would enter characters >> in a "search string". the "mode" would timeout after a 10 seconds. If a >> new character of the "search string" is read within the timeout period, >> the timer is renewed ("respooled"). If a non "search string" character >> is read, then the timer is cancelled and the "mode" exits. > This is exactly the scheme I need now and then, and the only kind of > task where I wanted `timer-activate'. You don't need `timer-activate` for that: just deactivate your original timer with `cancel-timer` and create a new one with `run-with-idle-timer` if you need that. Both of which are documented in the ELisp manual, contrary to `timer-activate`. Stefan