[9.4] LOGBOOK visibility - Kévin Le Gouguec

emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [9.4] LOGBOOK visibility
Date: Thu, 02 Jul 2020 12:19:12 +0200	[thread overview]
Message-ID: <87eepuz0bj.fsf@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

Hi,

I've noticed that LOGBOOK drawers are now (9.4) open by default when
visiting an Org file, AFAICT as a result of org-startup-folded now
defaulting to showeverything.

That's not much of a problem by itself; what I find more of a hindrance
is that even with "#+STARTUP overview", when one starts isearching for
something, all "nearby" LOGBOOK drawers are opened; this adds a lot of
visual noise that hides the document structure.

For example, in the attached file, if I search for "bug#5":

- Org 9.3 keeps the drawers closed,
- Org 9.4 opens every drawer for bugs 4, 5 and 6.

AFAICT Org 9.3 never opened these drawers unless either
org-startup-folded was showeverything, the user explicitly opened one
individually, or their /content/ matched a search.

Note that when cycling with S-TAB, even when "[SHOWING] ALL", Org 9.4
keeps these drawers closed.

Is there a knob I've missed that would allow me to tell Org to keep
LOGBOOKs closed?


BTW, while reading ORG-NEWS, I came across this bit, added in 074ea1629:

> *** Deprecated ~org-cycle-hide-drawers~ function
> 
> Use the new function ~org-hide-drawer-all~ instead.  Note that there
> is also a new ~org-cycle-hide-property-drawers~ function.

AFAICT org-cycle-hide-property-drawers has been removed in 1aa095ccf?


Thank you for your time, and for your work with Org 9.4.



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: logbooks.org --]
[-- Type: text/x-org, Size: 4010 bytes --]

#+STARTUP: overview
* project 1
** bug#1
*** investigate
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** fix
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** document
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
** bug#2
*** investigate
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** fix
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** document
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
** bug#3
*** investigate
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** fix
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** document
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
* project 2
** bug#4
*** investigate
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** fix
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** document
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
** bug#5
*** investigate
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** fix
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** document
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
** bug#6
*** investigate
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** fix
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:
*** document
:LOGBOOK:
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
CLOCK: [2020-07-02 Thu 11:43]--[2020-07-02 Thu 11:43] =>  0:00
:END:

next             reply	other threads:[~2020-07-02 10:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 10:19 Kévin Le Gouguec [this message]
2020-07-03 13:47 ` [9.4] LOGBOOK visibility Kévin Le Gouguec
2020-07-03 18:17   ` Kévin Le Gouguec
2020-07-04  2:53     ` Ihor Radchenko
2020-07-04  4:57       ` Ihor Radchenko
2020-07-04  8:03       ` Kévin Le Gouguec
2020-07-04  8:08       ` Nicolas Goaziou
2020-07-04  8:28         ` Kévin Le Gouguec
2020-07-04 11:18           ` Ihor Radchenko

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=87eepuz0bj.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).