Hi Carsten,
> I believe I have done it in the right place now, please confirm.
Confirmed, thanks, that's what I wanted.
There's just a little typo in the docstring of `org-unlogged-message':
"Display a message, but avoid loggin it in the *Messages* buffer."
^
On 6.8.2013, at 13:32, Michael Heerdegen wrote:
> 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,
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
Hi Bastien
On Sat, Dec 22, 2012 at 4:07 PM, Bastien wrote:
> Both `org-display-outline-path' and visibility cycling will not
> populate the *Message* buffer with messages anymore.
Nice, thank you.
Michael
Michael Brand writes:
> On Wed, Oct 31, 2012 at 5:27 PM, Michael Heerdegen
> 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
Hi all
On Wed, Oct 31, 2012 at 5:27 PM, Michael Heerdegen
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, th
Christopher Schmidt writes:
> +1, I totally agree. These message do not need to be logged into the
^^^
> *Messages*-buffer because this provides no benefit whatsoever.
s/message/messages
Christopher
Michael Heerdegen writes:
> 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.
>
> I'm not sure if this is the right thing in every case, but if the goal
> is to
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
-
