From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: D. Goel Newsgroups: gmane.emacs.devel Subject: Re: idledo.el v. 0.3 Date: 24 Oct 2002 10:25:39 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: <87elafykv0.fsf@computer.localdomain> References: <87wuobakqz.fsf@computer.localdomain> <5xfzuyqbxo.fsf@kfs2.cua.dk> <874rbduxdf.fsf@computer.localdomain> <5xbs5ljj6s.fsf@kfs2.cua.dk> <87u1jcq1ex.fsf@computer.localdomain> <5xy98ozpfj.fsf@kfs2.cua.dk> <87bs5kbuzm.fsf@computer.localdomain> <5xadl4p0xp.fsf@kfs2.cua.dk> <8765vshwgx.fsf@computer.localdomain> <5xznt3op18.fsf@kfs2.cua.dk> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035469891 22817 80.91.224.249 (24 Oct 2002 14:31:31 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 24 Oct 2002 14:31:31 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 184j1F-0005vq-00 for ; Thu, 24 Oct 2002 16:31:29 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 184j3S-0006yD-00 for ; Thu, 24 Oct 2002 16:33:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 184iwN-0002c7-00; Thu, 24 Oct 2002 10:26:27 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 184ivj-0001EZ-00 for emacs-devel@gnu.org; Thu, 24 Oct 2002 10:25:47 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 184ive-00013I-00 for emacs-devel@gnu.org; Thu, 24 Oct 2002 10:25:46 -0400 Original-Received: from 24-197-159-102.charterga.net ([24.197.159.102] helo=computer) by monty-python.gnu.org with esmtp (Exim 4.10) id 184ivd-00011t-00 for emacs-devel@gnu.org; Thu, 24 Oct 2002 10:25:41 -0400 Original-Received: from deego by computer with local (Exim 3.36 #1 (Debian)) id 184ivb-0005pS-00; Thu, 24 Oct 2002 10:25:39 -0400 Original-To: storm@cua.dk (Kim F. Storm) X-Face: %s/\3ns|d/_z'KxGk~\(u3yH5N/i1O]T?"}9sD1V5v,()NA0""Cm{'jN*hom1vJtXdS."1! 7@m1$XpG\hHWZD;>{gIck?A3MzE/ap9+k5HTU;>4q-4Q""]9aszKsVe5uS8D9Xnxm4psT[x4 In-Reply-To: <5xznt3op18.fsf@kfs2.cua.dk> Original-Lines: 68 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:8735 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8735 storm@cua.dk (Kim F. Storm) writes: > > IMHO, This one is the only "important" case that does not get covered. > > Though it may seldom be needed in practice, it would seem awkward to > > leave this out. > > I honestly fail to see how that is of any practical use. I agree about the not-of-much-practical use thingy.. I was more concerned about "doing the right thing" --- all other "missing" functionalitites can easily be implemented the user herself by tweaking their function (and hence of no more concern to me) . The above was the only remaining case which i didn't see a way that user could implement --- i thought that if, for some weird impractical reason, they want to implement such a timer, they would have to go back to using either the sit-for (as in timerfunctions.el) or pre-command-hook (as in blink-cursor-mode), both of which seem kludgy and "wrong". > But it could be handled by overloading the REPEAT argument so that > if it is a negative number, it means repeat every -REPEAT seconds > after first being idle, but don't repeat on next emacs idle. I like this one too! :) > > Yes, that's always a possibility ... actually, it would seem to be > useful to also have a "no longer idle" handler for an idle-timer which Indeed. > I suppose your primary interest is to be able to know whether a given > idle-timer is activated for the first time after emacs becoming idle > , or whether it is a repeated activation in the same idle period; Exactly. > for that purpose, the first element of the timer vector could > provide the necessary information (as it would be t on first > invocation). If this is so, then I am indeed satisfied. :) ... BTW, I think there's not documentation for what exactly the idle-timer vector stores [other than one layout-line], anywhere. Neither in the elisp manual, nor in timer.el . Moreover, it seemed that was not easy to figure that stuff out from even studying the lisp code of timer.el, it seems the only way would be to try to study the C code :( (In particular, it is not clear to me why the triggerred-p (the first element of the timer-vector) would not be t on subsequent invocations within a given idle-period, as you mention above.) So, if the maintainers/experts of timer.el (Kim?) get this mail, we the users would appreciate some info on the timer-vector in the manual or elsewhere :) DG http://deego.gnufans.org/~deego/ -- RMS on Treacherous Computing and Digital Restrictions Management --- http://newsforge.com/newsforge/02/10/21/1449250.shtml?tid=19