From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: undo in loaddefs.el buffer Date: Sat, 01 Jan 2005 00:25:14 -0500 Message-ID: References: <200412211414.iBLEEZ903426@raven.dms.auburn.edu> <200412211541.iBLFfBc03861@raven.dms.auburn.edu> <87llbonyup.fsf@jurta.org> <200412260206.iBQ26wG17970@raven.dms.auburn.edu> <41CEE3B8.9090600@swipnet.se> <200412270231.iBR2VDE19709@raven.dms.auburn.edu> <41CFE247.8090409@swipnet.se> <200412280503.iBS53deD002564@manatee.dms.auburn.edu> <200412290207.iBT27Gk0006913@manatee.dms.auburn.edu> <200412300114.iBU1EY001351@moose.dms.auburn.edu> <200412310154.iBV1s5w05229@raven.dms.auburn.edu> <200412311504.iBVF4QO05860@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1104557536 3081 80.91.229.6 (1 Jan 2005 05:32:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 1 Jan 2005 05:32:16 +0000 (UTC) Cc: juri@jurta.org, yamaoka@jpl.org, jan.h.d@swipnet.se, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 01 06:32:09 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Ckbs1-0002MC-00 for ; Sat, 01 Jan 2005 06:32:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Ckc33-0007F2-JQ for ged-emacs-devel@m.gmane.org; Sat, 01 Jan 2005 00:43:33 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Ckc2p-0007BN-6z for emacs-devel@gnu.org; Sat, 01 Jan 2005 00:43:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Ckc2m-00079h-8Z for emacs-devel@gnu.org; Sat, 01 Jan 2005 00:43:16 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Ckc2m-000799-1K for emacs-devel@gnu.org; Sat, 01 Jan 2005 00:43:16 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CkbrH-00039I-He for emacs-devel@gnu.org; Sat, 01 Jan 2005 00:31:23 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1CkblK-0003Rh-Mi; Sat, 01 Jan 2005 00:25:14 -0500 Original-To: Luc Teirlinck In-reply-to: <200412311504.iBVF4QO05860@raven.dms.auburn.edu> (message from Luc Teirlinck on Fri, 31 Dec 2004 09:04:26 -0600 (CST)) 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: main.gmane.org gmane.emacs.devel:31651 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:31651 All known examples write into buffers that are current No, most timers do not. I found about 40 places in Emacs that create timers, and these are just two of them. There is no need for the manual to explain all the ways of writing code that could possibly be made to work. That is not the manual's job. However, I found a simple way to improve the text. It is normal that there is code in Emacs that does things the manual says users shouldn't do. Writing the manual in such a way that no code in Emacs ever goes against its recommendations is not the goal. And they have to take special measures to deal with the consequences of violating the rule. Some of which are obvious and some of which are non-obvious. My proposal is to point out the latter. Could you please explain these special requirements in the comments in autorevert.el, if that isn't already done.