From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Heerdegen Subject: Re: Bug: Messaging when moving in the agenda [7.9.2 (7.9.2-GNU-Emacs-24-3 @ /usr/share/emacs/24.2.50/lisp/org/)] Date: Tue, 06 Aug 2013 13:32:39 +0200 Message-ID: <87pptrdpgo.fsf@web.de> References: <87bofivc8b.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33822) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6fhR-0000BE-IL for emacs-orgmode@gnu.org; Tue, 06 Aug 2013 07:45:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V6fhK-0006OE-6R for emacs-orgmode@gnu.org; Tue, 06 Aug 2013 07:45:13 -0400 Received: from plane.gmane.org ([80.91.229.3]:53526) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V6fhJ-0006Kj-UV for emacs-orgmode@gnu.org; Tue, 06 Aug 2013 07:45:06 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1V6fhH-0005vz-M2 for emacs-orgmode@gnu.org; Tue, 06 Aug 2013 13:45:03 +0200 Received: from ip-2-201-214-118.web.vodafone.de ([2.201.214.118]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Aug 2013 13:45:03 +0200 Received: from michael_heerdegen by ip-2-201-214-118.web.vodafone.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 06 Aug 2013 13:45:03 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hello, > When I move around in the *Org Agenda* with up and down, the current > outline path is displayed in the echo area, which is good. > > However, what is displayed gets also copied in the *Messages* buffer, > which is not helpful, but clutters *Messages* with useless noise. > > So, IMHO `org-display-outline-path' should still display its stuff in > the echo area, but prevent logging in *Messages*. AFAIK, the way to do > this is to bind `message-log-max' to nil. Can we please try to make some progress here? I don't want to suggest a patch because I don't know the org code base well, but binding `message-log-max' to nil at one or two location should totally suffice. Who can help? Regards, Michael.