From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: Time zone support for agenda item timestamps Date: Sat, 9 Apr 2011 17:54:08 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from [140.186.70.92] (port=45858 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q8aUF-0003BJ-2T for emacs-orgmode@gnu.org; Sat, 09 Apr 2011 11:54:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q8aUD-0007iG-SW for emacs-orgmode@gnu.org; Sat, 09 Apr 2011 11:54:10 -0400 Received: from mail-iw0-f169.google.com ([209.85.214.169]:65262) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q8aUD-0007iB-MX for emacs-orgmode@gnu.org; Sat, 09 Apr 2011 11:54:09 -0400 Received: by iwg8 with SMTP id 8so5802839iwg.0 for ; Sat, 09 Apr 2011 08:54:08 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Matt Curtis Cc: emacs-orgmode@gnu.org Hi Matt I know only of an old thread about this http://thread.gmane.org/gmane.emacs.orgmode/5145 Of course it would be very welcome and valuable for e. g. traveling but I fear it is now too expensive to introduce. The trouble I see is that the smallest possible first change has to include already almost all of the work to be done in order to not break any of the many things that are supported now and to hold on with backwards compatibility. I hope that there are ideas that I can not imagine now, how this could be broken down into reasonable parts. Michael On Sat, Apr 9, 2011 at 12:23, Matt Curtis wrote: > Hello, > > I would like agenda timestamps to support time zones somehow, and I'm after > some guidance from org-mode developers. > > My plan is to support the time offset +HHMM or -HHMM, at a minimum. > > After looking at the code I believe I need to modify org-agenda-get-timestamps > quite heavily to effect this change. > > Currently it looks like it scans for timestamps which match the search date > (YYYY-MM-DD), which would need to be changed to at least match adjacent > days, and then filtered after applying the time zone offset, and > finally adjusted > with the offset to match local time. > > This would mean the agenda/list displays would get the same sort of results > set, as the timestamps would be adjusted back to the search date - i.e. the > search date would be considered "local time"; the change is to consider the > offset when figuring out which items fall on this date. > > I have a couple of questions: > > * Is this a reasonable approach? (It would slow down agenda generation > with the extra scanning and filtering) > > * If not, is there another design I can look at? (I wonder why this hasn't been > done before, so I think maybe others have done some thinking about it.) > > * What parts of org-mode should I be looking at to ensure this change does > not cause a regression?