emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: michael_heerdegen@web.de, Org Mode <emacs-orgmode@gnu.org>
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: Sat, 22 Dec 2012 16:07:30 +0100	[thread overview]
Message-ID: <87wqw9y823.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CALn3zojhRNBx9kw=DWqAtCuXLwfmUQ35Detoh6nJLT_ugmZ6hQ@mail.gmail.com> (Michael Brand's message of "Thu, 8 Nov 2012 15:17:13 +0100")

Michael Brand <michael.ch.brand@gmail.com> writes:

> On Wed, Oct 31, 2012 at 5:27 PM, Michael Heerdegen
> <michael_heerdegen@web.de> wrote:
>> So, IMHO `org-display-outline-path' should still display its stuff in
>> the echo area, but prevent logging in *Messages*.
>
> I also agree. Until now I assumed that this would not be possible
> because I didn't know about:
>
>> AFAIK, the way to do this is to bind `message-log-max' to nil.
>> [...]
>> Dunno if there are other functions that could benefit from the same
>> treatment.
>
> At least also visibility cycling.

Both `org-display-outline-path' and visibility cycling will not
populate the *Message* buffer with messages anymore.  Thanks for
this suggestion.

-- 
 Bastien

  reply	other threads:[~2012-12-22 23:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 16:27 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/)] Michael Heerdegen
2012-11-07 19:28 ` Christopher Schmidt
2012-11-07 19:33   ` Christopher Schmidt
2012-11-08 14:17 ` Michael Brand
2012-12-22 15:07   ` Bastien [this message]
2012-12-23  9:47     ` Michael Brand
2013-08-06 11:32 ` Michael Heerdegen
2013-08-31  6:43   ` Carsten Dominik
2013-09-02 13:17     ` Michael Heerdegen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wqw9y823.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael.ch.brand@gmail.com \
    --cc=michael_heerdegen@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).