From: "Christof Musik" <ml-orgmode@litephone.org>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Bug: Updating clocktable hides other content [9.0.5 (9.0.5-elpa @ /home/christof/.emacs.d/elpa/org-20170210/)]
Date: Sat, 25 Mar 2017 23:37:56 +0100 [thread overview]
Message-ID: <kcim.58d6f144.2ffa.6d6fe7b42f60fa37@wist.senfdax.de> (raw)
Hi
I have noticed some problems on updating a clocktable in a dynamic block.
If you update this table with org-dblock-update, then all content besides that table
is hidden. I have not found a way to show it again without opening the file again.
Example:
----
* bar
* baz
* foo
#+BEGIN: clocktable :maxlevel 2 :scope subtree
#+CAPTION: Clock summary at [2017-03-25 Sa 23:19]
| Headline | Time | |
|--------------+--------+------|
| *Total time* | *2:00* | |
|--------------+--------+------|
| foo | 2:00 | |
| \_ TODO a | | 1:00 |
| \_ TODO b | | 1:00 |
#+END:
** TODO a
CLOCK: [2017-03-25 Sa 21:32]--[2017-03-25 Sa 22:32] => 1:00
** TODO b
CLOCK: [2017-03-24 Fr 21:32]--[2017-03-24 Fr 22:32] => 1:00
----
Steps to reproduce:
Go to the line with "BEGIN" and press C-c C-C (org-dblock-update).
Now only the header foo is shown and bar, baz are hidden. Saving the file does
not kill them, but without opening the file again they won't come back.
I have also bisected this and found that the commit 33f8f8adaaa2a2458f7489f0ec714a230e981823
is the culprit for this behavior. Hope this helps as my Lisp knowledge is very limited.
------------------------------------------------------------------------
Emacs : GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.22.7)
of 2017-02-07
Package: Org mode version 9.0.5 (9.0.5-elpa @ /home/christof/.emacs.d/elpa/org-20170210/)
Kind regards
Christof Musik
next reply other threads:[~2017-03-25 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 22:37 Christof Musik [this message]
2017-03-28 1:36 ` Bug: Updating clocktable hides other content [9.0.5 (9.0.5-elpa @ /home/christof/.emacs.d/elpa/org-20170210/)] Yasushi SHOJI
2017-03-29 14:35 ` Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kcim.58d6f144.2ffa.6d6fe7b42f60fa37@wist.senfdax.de \
--to=ml-orgmode@litephone.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.