From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: rasmith@tamu.edu Newsgroups: gmane.emacs.help Subject: Problem with messages Date: Tue, 30 Mar 2010 18:31:47 -0500 (CDT) Message-ID: <20100330.183147.119882394802354622.rasmith@aristotle.tamu.edu> Reply-To: rasmith@tamu.edu NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1269991950 683 80.91.229.12 (30 Mar 2010 23:32:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 30 Mar 2010 23:32:30 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Mar 31 01:32:26 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Nwkv1-0000Kn-3R for geh-help-gnu-emacs@m.gmane.org; Wed, 31 Mar 2010 01:32:23 +0200 Original-Received: from localhost ([127.0.0.1]:48098 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nwkv0-0006Gy-Dc for geh-help-gnu-emacs@m.gmane.org; Tue, 30 Mar 2010 19:32:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nwkud-0006Gt-4I for help-gnu-emacs@gnu.org; Tue, 30 Mar 2010 19:31:59 -0400 Original-Received: from [140.186.70.92] (port=35422 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nwkub-0006Gd-1n for help-gnu-emacs@gnu.org; Tue, 30 Mar 2010 19:31:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NwkuZ-0006cC-I9 for help-gnu-emacs@gnu.org; Tue, 30 Mar 2010 19:31:56 -0400 Original-Received: from aristotle.tamu.edu ([128.194.75.5]:29238) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NwkuZ-0006bu-Cs for help-gnu-emacs@gnu.org; Tue, 30 Mar 2010 19:31:55 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by aristotle.tamu.edu (Postfix) with ESMTP id CD770E042D for ; Tue, 30 Mar 2010 18:31:47 -0500 (CDT) X-Mailer: Mew version 6.3 on Emacs 23.1 / Mule 6.0 (HANACHIRUSATO) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:72549 Archived-At: Since moving to emacs-23.1, I've encountered a problem with some elisp code I use regularly. I won't try to explain the whole context, but in a few words, the code processes a buffer containing text in a specialized format and then returns in that buffer. The problem is that it now displays the message "Mark set" in the minibuffer on return, and that message doesn't want to go away. For example, if I do an isearch, "Mark set" remains in the minibuffer until (usually) I enter the *second* character in the string, and at that point I get the usual isearch message (string so far, etc.); then, on the third or fourth character, it will come back, perhaps hang around for another character or two, then disappear, etc. Other commands that return a message in the minibuffer such as what-cursor (C-x =) just don't return at all ("Mark set" stays there). Under emacs22, this same code worked with no problems. I realize this could have many different causes, but does anyone have a quick idea about what might be causing this? FWIW, the code that produces the buffer doesn't have set-mark or push-mark in it. Thanks, Robin Smith Department of Philosophy rasmith@tamu.edu Texas A&M University http://aristotle.tamu.edu/~rasmith/ 4237 TAMU Voice +1 979 845 5679 College Station, TX 77843-4237 FAX +1 979 845 0458