From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Blunderbuss ".dir-locals.el" raises everything in its path!! Date: Thu, 16 Jul 2009 14:38:35 -0400 Message-ID: References: <20090712144137.GB2524@muc.de> <87hbxhony6.fsf@stupidchicken.com> <20090712180623.GA1009@muc.de> <87k52dycha.fsf@stupidchicken.com> <4A5C2C96.4080802@swipnet.se> <43507.130.55.118.19.1247580320.squirrel@webmail.lanl.gov> <20090714151327.GA1718@muc.de> <53864.130.55.118.19.1247586358.squirrel@webmail.lanl.gov> <87r5whgzvg.fsf@mail.jurta.org> <0C244EB2B99349238E281268B0339C72@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1247769597 26276 80.91.229.12 (16 Jul 2009 18:39:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 16 Jul 2009 18:39:57 +0000 (UTC) Cc: 'Juri Linkov' , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 16 20:39:50 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MRVrw-0007kZ-3I for ged-emacs-devel@m.gmane.org; Thu, 16 Jul 2009 20:39:48 +0200 Original-Received: from localhost ([127.0.0.1]:36354 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MRVrv-0000H2-CY for ged-emacs-devel@m.gmane.org; Thu, 16 Jul 2009 14:39:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MRVqt-0007Qf-Ua for emacs-devel@gnu.org; Thu, 16 Jul 2009 14:38:44 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MRVqo-0007IA-KR for emacs-devel@gnu.org; Thu, 16 Jul 2009 14:38:42 -0400 Original-Received: from [199.232.76.173] (port=53694 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MRVqo-0007Hr-D0 for emacs-devel@gnu.org; Thu, 16 Jul 2009 14:38:38 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:25441 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MRVqo-0001C1-2k for emacs-devel@gnu.org; Thu, 16 Jul 2009 14:38:38 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq8EAOAQX0rO+LUT/2dsb2JhbACBUdF8hA0FhnU X-IronPort-AV: E=Sophos;i="4.42,412,1243828800"; d="scan'208";a="41745602" Original-Received: from 206-248-181-19.dsl.teksavvy.com (HELO pastel.home) ([206.248.181.19]) by ironport2-out.teksavvy.com with ESMTP; 16 Jul 2009 14:38:35 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 70E8780B0; Thu, 16 Jul 2009 14:38:35 -0400 (EDT) In-Reply-To: <0C244EB2B99349238E281268B0339C72@us.oracle.com> (Drew Adams's message of "Thu, 16 Jul 2009 09:43:20 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:112548 Archived-At: >> I think `message' should be improved to collect all messages coming >> in quick succession and display all of them appended to the echo area. > Certainly not as the default behavior. Perhaps as an alternative behavior. > There is lots of code, I'm sure, that depends on one message supplanting a > previous message. That is, the user is _supposed_ to see only the latest > message, not a concatenation of the last several messages. Agreed, it needs to be a new function. Maybe we could create a new function (notify-user MSG &rest ARGS) which would return immediately but display something in the echo area (or at the end of the minibuffer) for (at least?) notify-user-time seconds. Several successive calls to it would just queue up messages that are later displayed in turn (probably with some sort of "compaction" feature so repeated messages don't bore the user to death). Maybe it should be integrated/combined with the display-warning facility. Stefan