From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: wrapper fn for message and minibuffer-message? Date: Thu, 06 Oct 2005 01:28:15 -0400 Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1128576547 27660 80.91.229.2 (6 Oct 2005 05:29:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 6 Oct 2005 05:29:07 +0000 (UTC) Cc: drew.adams@oracle.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 06 07:29:06 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ENOIr-0001FG-5D for ged-emacs-devel@m.gmane.org; Thu, 06 Oct 2005 07:28:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ENOIq-0003B2-KI for ged-emacs-devel@m.gmane.org; Thu, 06 Oct 2005 01:28:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ENOIi-0003Al-LV for emacs-devel@gnu.org; Thu, 06 Oct 2005 01:28:16 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ENOIi-0003AZ-8b for emacs-devel@gnu.org; Thu, 06 Oct 2005 01:28:16 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ENOIi-0003AW-5Q for emacs-devel@gnu.org; Thu, 06 Oct 2005 01:28:16 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ENOIi-0000w3-9h for emacs-devel@gnu.org; Thu, 06 Oct 2005 01:28:16 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1ENOIh-0000TP-3V; Thu, 06 Oct 2005 01:28:15 -0400 Original-To: Stefan Monnier In-reply-to: (message from Stefan Monnier on Wed, 05 Oct 2005 11:53:57 -0400) 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: news.gmane.org gmane.emacs.devel:43605 Archived-At: I'd even argue that this function should be called "minibuffer-message", since currently minibuffer-message is only used when (minibufferp) is non-nil. I agree that is a natural generalization. But I agree that this name is not very clear for the current behavior, and even less clear for the suggested behavior. I can't think of a better name for this function, but I do have an idea for a cleaner interface for the feature. Have a variable minibuffer-message-at-end which, if t, causes `message' to display messages this way. It could use the same mechanism as now; or, maybe it would be cleaner to change the lower levels of redisplay to display the message at the end of the minibuffer when it is selected.