Re: [O] 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/)]

2013-09-02 Thread Michael Heerdegen
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.
^
g

Regards,

Michael.



Re: [O] 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/)]

2013-08-31 Thread Carsten Dominik

On 6.8.2013, at 13:32, Michael Heerdegen michael_heerde...@web.de 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, 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?

Mi Michael,

I believe I have done it in the right place now, please confirm.

Thanks

- Carsten

 
 
 Regards,
 
 Michael.
 
 




Re: [O] 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/)]

2013-08-06 Thread Michael Heerdegen
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.




Re: [O] 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/)]

2012-12-23 Thread Michael Brand
Hi Bastien

On Sat, Dec 22, 2012 at 4:07 PM, Bastien b...@altern.org wrote:
 Both `org-display-outline-path' and visibility cycling will not
 populate the *Message* buffer with messages anymore.

Nice, thank you.

Michael



Re: [O] 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/)]

2012-12-22 Thread Bastien
Michael Brand michael.ch.br...@gmail.com writes:

 On Wed, Oct 31, 2012 at 5:27 PM, Michael Heerdegen
 michael_heerde...@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



Re: [O] 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/)]

2012-11-08 Thread Michael Brand
Hi all

On Wed, Oct 31, 2012 at 5:27 PM, Michael Heerdegen
michael_heerde...@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.

Michael



Re: [O] 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/)]

2012-11-07 Thread Christopher Schmidt
Michael Heerdegen michael_heerde...@web.de 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 just display something for better orientation etc., there is no
 need for logging.

+1, I totally agree.  These message do not need to be logged into the
*Messages*-buffer because this provides no benefit whatsoever.

Christopher



Re: [O] 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/)]

2012-11-07 Thread Christopher Schmidt
Christopher Schmidt christop...@ch.ristopher.com 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



[O] 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/)]

2012-10-31 Thread Michael Heerdegen

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.


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.

I'm not sure if this is the right thing in every case, but if the goal
is to just display something for better orientation etc., there is no
need for logging.

Dunno if there are other functions that could benefit from the same
treatment.


Regards,

Michael.

Emacs  : GNU Emacs 24.2.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2)
 of 2012-10-25 on dex, modified by Debian
Package: Org-mode version 7.9.2 (7.9.2-GNU-Emacs-24-3 @ 
/usr/share/emacs/24.2.50/lisp/org/)

current state:
==
(setq
 org-export-preprocess-before-selecting-backend-code-hook 
'(org-beamer-select-beamer-code)
 org-tab-first-hook '(org-hide-block-toggle-maybe 
org-src-native-tab-command-maybe
  org-babel-hide-result-toggle-maybe 
org-babel-header-arg-expand)
 org-agenda-skip-deadline-prewarning-if-scheduled t
 org-speed-command-hook '(org-speed-command-default-hook 
org-babel-speed-command-hook)
 org-reverse-note-order t
 org-occur-hook '(org-first-headline-recenter)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-capture-after-finalize-hook '(#[nil \300\301!\207 [org-agenda-to-appt 
refresh] 2])
 org-export-preprocess-before-normalizing-links-hook 
'(org-remove-file-link-modifiers)
 org-confirm-shell-link-function 'yes-or-no-p
 org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc
   org-beamer-auto-fragile-frames
   org-beamer-place-default-actions-for-lists)
 org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
 org-agenda-skip-scheduled-if-done t
 org-agenda-custom-commands '((d todo DELEGATED nil) (c todo 
DONE|DEFERRED|CANCELLED nil)
  (w todo WAITING nil) (W agenda #1= 
((org-agenda-ndays 21)))
  (A #A Tasks for today agenda #1#
   ((org-agenda-skip-function
 (lambda nil
  (org-agenda-skip-entry-if (quote notregexp) 
\\=.*\\[#A\\]))
 )
(org-agenda-ndays 1)
(org-agenda-overriding-header Today's Priority 
#A tasks: ))
   )
  (u Unsceduled Tasks alltodo #1#
   ((org-agenda-skip-function
 (lambda nil
  (org-agenda-skip-entry-if (quote scheduled) 
(quote deadline)
   (quote regexp) [^\n]+)
  )
 )
(org-agenda-overriding-header Unscheduled TODO 
entries: ))
   )
  )
 org-return-follows-link t
 org-capture-templates '((t Task entry (file+headline my-org-todo-file 
Tasks)
  * TODO %?\n  SCHEDULED: %t :prepend t)
 (a APPT entry (file+headline my-org-todo-file 
Tasks) * APPT %?\n  %t
  :prepend t)
 (c FromConkeror entry (file+headline 
my-org-todo-file Tasks)
  * TODO %?\n  :PROPERTIES:\n  :created: %U\n  :link: 
%a\n  :END:\n  %i
  :prepend t)
 )
 org-after-todo-state-change-hook '(org-clock-out-if-current)
 org-from-is-user-regexp \\Michael Heerdegen\\
 org-src-mode-hook '(org-src-babel-configure-edit-buffer 
org-src-mode-configure-edit-buffer)
 org-agenda-before-write-hook '(org-agenda-add-entry-text)
 org-babel-pre-tangle-hook '(save-buffer)
 org-mode-hook '((lambda (rest --cl-rest--)
  (apply
   (quote
#[(#1=#:G76352 #:G76353 rest #2=#:arguments_76338) 
\302J@\\207
  [#1# #2# apply] 3]
)
   (quote #:--wrapped-lambda_76337--) (quote #:--menu--) 
--cl-rest--)
  )
 #[nil \300\301\302\303\304$\207
   [org-add-hook change-major-mode-hook org-show-block-all 
append local] 5]
 #[nil \300\301\302\303\304$\207