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: [gareth.jones@stud.man.ac.uk: Re: pop3-read-response not robust in the presence of timers] Date: Mon, 28 Apr 2003 00:38:04 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1051504892 11415 80.91.224.249 (28 Apr 2003 04:41:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 28 Apr 2003 04:41:32 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Apr 28 06:41:30 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19A0Rs-0002x2-00 for ; Mon, 28 Apr 2003 06:41:04 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19A0Zt-0007LO-00 for ; Mon, 28 Apr 2003 06:49:21 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19A0RI-0004Pg-0C for emacs-devel@quimby.gnus.org; Mon, 28 Apr 2003 00:40:28 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 19A0QS-000435-00 for emacs-devel@gnu.org; Mon, 28 Apr 2003 00:39:36 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 19A0Q0-0003fO-00 for emacs-devel@gnu.org; Mon, 28 Apr 2003 00:39:09 -0400 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19A0P0-0003DI-00 for emacs-devel@gnu.org; Mon, 28 Apr 2003 00:38:06 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.10) id 19A0Oy-0001uO-00; Mon, 28 Apr 2003 00:38:04 -0400 Original-To: Lars Magne Ingebrigtsen In-reply-to: (message from Lars Magne Ingebrigtsen on Sun, 27 Apr 2003 03:59:29 +0200) Original-cc: zsh@cs.rochester.edu X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:13496 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:13496 One could also approach this from the opposite side -- slapping (the equivalent of) `save-buffer-excursion' around the timer functions That would be one way to implement it for all the functions that can run timers, including accept-process-output, read-event and read-key-sequence. Still, the question is, is it ok to make the change that timers can't change the current buffer. Can anyone think of a situation where this would be a problem? Would someone like to look through the code base and see if any timer needs to change the current buffer?