Jambunathan K <kjambunat...@gmail.com> writes: > Try this: > > (defadvice org-cycle-internal-local > (around org-cycle-internal-local-suppress-messages activate) > "Do the local cycling action, but suppress messages." > (letf (((symbol-function 'message) (symbol-function 'ignore))) > ad-do-it)) > > (defadvice org-cycle-internal-global > (around org-cycle-internal-global-suppress-messages activate) > "Do the global cycling action, but suppress messages." > (letf (((symbol-function 'message) (symbol-function 'ignore))) > ad-do-it)) > > You can also use `flet' form to `ignore' the `message'.
Thats nice, thank you. On the other hand, I wonder if it wouldn't make sense to add my "patch" to org.el, since unconditionally writing messages for every visibility-state change produces quite a lot of clutter, so the user should be able to turn this off IMO. > Thorsten Jolitz <tjol...@gmail.com> writes: > >> Hi List, >> >> when calling Org-mode functionality form an external program, some >> functions seem to make use of 'org-cycle', what results in a lot of >> "OVERVIEW" messages arriving at stdout/stderr >> >> ,--------- >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | OVERVIEW >> | .... >> `--------- >> >> >> that are not really helpful and a bit of a hassle. >> >> ,------------------------------------------------------------------------- >> | (org-cycle &optional ARG) >> | .... >> | >> | - When this function is called with a prefix argument, rotate the entire >> | buffer through 3 states (global cycling) >> | 1. OVERVIEW: Show only top-level headlines. >> | 2. CONTENTS: Show all headlines of all levels, but no body text. >> | 3. SHOW ALL: Show everything. >> `------------------------------------------------------------------------- >> >> Is there a way to turn these message off? I found things like >> 'org-no-popups or 'org-no-warnings but nothing like >> "org-no-visibility-state-messages" or so. Its not really a big problem, >> rather an inconvenience, but maybe its easy to solve when knowing where >> to look. > > -- cheers, Thorsten
