From: Vincent Beffara <email@example.com>
To: Org Mode List <firstname.lastname@example.org>
Subject: Bug in org-agenda.el (Was: Bad time display in agenda view)
Date: Tue, 15 Jan 2013 14:32:41 +0100 [thread overview]
Message-ID: <4B7BFC3F046C4630A39578921F322E7C@gmail.com> (raw)
Ha, I got it !
When displaying the end time of an interval in agenda view, org-agenda transforms the initial time stamp to minutes, adds the default length to that and maps back to a time stamp using org-minutes-to-clocksum-string. The problem being that this functions checks org-time-clocksum-use-effort-durations and if set to t, uses that in the formatting. Meaning that "8:00" is displayed as "1d 0:00" instead, and "17:30" as "2d 1:30" and so on.
I am afraid to change the code, so I just customized org-time-clocksum-use-effort-durations to nil and everything works for now. But presumably this should be fixed by letting it be nil while formatting the end timestamp, somewhere near line 6404 of org-agenda.el ?
On Monday, January 14, 2013 at 11:50 , Vincent Beffara wrote:
> Updated org today (release_7.9.3d-823-gd06fa4), and the times displayed in agenda-view for events of default duration look as if the duration was chosen to be 17 hours: I get this,
> Talks: 14:30-1d 7:30sdf : lskdfjlskdjf
> Talks: 17:30-18:30 sdfsdfs : sdf
> (Here the second one has a timestamp like <... 17:30-18:30> and the first one like <... 14:30>.) Everything works out when pushed using org-caldav, so I believe this is just hapening during display. What is happening ?
> BTW, my org-agenda-default-appointment-duration is set to 60.
> Vincent Beffara
next prev parent reply other threads:[~2013-01-15 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 10:50 Bad time display agenda view Vincent Beffara
2013-01-15 13:32 ` Vincent Beffara [this message]
2013-01-15 19:19 ` Bug in org-agenda.el Achim Gratz
2013-01-22 14:54 ` Bastien
2013-01-22 17:20 ` Achim Gratz
2013-01-22 14:53 ` Bastien
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 \
* 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).