Can someone please verify these bugs? Thanks. Derek
Derek Upham writes: > I tried running org-timeline on an Org file with lots of timestamped > TODO -> DONE state changes, and didn't see the matches I was expecting. > While poking around, I found two problems. > > 1. `org-timeline' isn't setting the text properties necessary to refresh > the timeline buffer. This means that none of the special keys to update > the display actually work. Here's the `org-timeline' version: > > (add-text-properties (point-min) (point-max) '(org-agenda-type timeline)) > > Here's the same chunk in `org-agenda-list' for comparison: > > (add-text-properties (point-min) (point-max) > `(org-agenda-type agenda > org-last-args (,arg ,start-day ,span) > org-redo-cmd ,org-agenda-redo-command > org-series-cmd ,org-cmd)) > > 2. Even when the `org-timeline' function has refresh set up properly, > `org-agenda-log-mode' (via the `l' hotkey) doesn't work. It looks like > the function changes the buffer-local copy of the `org-agenda-show-log' > variable, but the refresh code looks at the global version of the > variable (possibly because the refresh is happening through eval?). In > order to see the log entries, you need to set `org-agenda-show-log' > outside of the timeline buffer (using `setq'). > > Can someone take a look at these? This is all with the latest sources > from the repo. Thanks. > > Derek
