emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Derek Upham <sand@blarg.net>
To: emacs-orgmode@gnu.org
Subject: org-agenda-show-log, org-timeline bugs
Date: Mon, 04 Feb 2013 00:33:31 -0800	[thread overview]
Message-ID: <87sj5cjx5w.fsf@priss.frightenedpiglet.com> (raw)

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 Upham

             reply	other threads:[~2013-02-04  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  8:33 Derek Upham [this message]
2013-02-07 15:00 ` org-agenda-show-log, org-timeline bugs Derek Upham
2013-02-13 11:54   ` Bastien
2013-02-17  0:54     ` Derek Upham
2013-04-13  9:47 ` Bastien

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:

  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=87sj5cjx5w.fsf@priss.frightenedpiglet.com \
    --to=sand@blarg.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).