From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Cross Subject: Re: Bug: org-2ft and/or float-time is wrong [9.1.2 (9.1.2-22-ga2a034-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20171023/)] Date: Thu, 02 Nov 2017 14:27:23 +1100 Message-ID: <87o9oll5r8.fsf@gmail.com> References: <87bmknkwhe.fsf@nicolasgoaziou.fr> <87tvyfjgjk.fsf@nicolasgoaziou.fr> <87tvyelb60.fsf@gmail.com> <87shdykuxc.fsf@gmail.com> <87r2thlewz.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59537) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eA6AF-0006CL-Gv for emacs-orgmode@gnu.org; Wed, 01 Nov 2017 23:27:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eA6AE-0003fY-E0 for emacs-orgmode@gnu.org; Wed, 01 Nov 2017 23:27:31 -0400 Received: from mail-pf0-x234.google.com ([2607:f8b0:400e:c00::234]:56010) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eA6AE-0003fK-81 for emacs-orgmode@gnu.org; Wed, 01 Nov 2017 23:27:30 -0400 Received: by mail-pf0-x234.google.com with SMTP id 17so3534386pfn.12 for ; Wed, 01 Nov 2017 20:27:30 -0700 (PDT) In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Allen Li Cc: emacs-orgmode@gnu.org, Nicolas Goaziou Allen Li writes: > On Wed, Nov 1, 2017 at 5:09 PM, Tim Cross wrote: >> >> Let me try to clarify and see if that helps. >> >> Org is only forcing time into UTC format for functions which deal with >> time comparisons. i.e. those which use org-2ft. The reason for doing >> this is to try and avoid issues relating to daylight savings timezone >> changes when performing comparison operations. >> >> It is not clear to me exactly how this is actually creating a problem >> for your scenario as there does not seem to be anywhere in org where >> values created by org-2ft are converted back to human readable time >> strings. If you can provide more details on how this is a practical >> issue in org-mode that might help. > > I think I made the problem quite clear multiple times. > > Assuming today is 2017-10-31, SCHEDULED<"" will match results > that have SCHEDULED=<2017-11-01> depending on your local time zone. > I get that, what I am not clear about is where you encounter this issue when using org .eg. is it when entering now as a date for generating an agenda of past or current scheduled items etc or is this a problem with some custom functions you have written where you need to enter 'now' manually and due to the use of UTC in time comparisons are forced to adjust manually for UTC or something else? This is what is not clear. From my own use, I don't see the issue you describe with scheduled items not appearing or appearing when they shouldn't, so don't know how to reproduce the issue your having i.e. when I do agenda searches, I don't see deadline or scheduled items showing up when they should not etc. This matters because if the issue is the former, then we likely do have a real bug. However, if it is the latter, then it may be a bug or it may be just an implementation weakness or it could just be a difference of opinions on how it should be. Your examples don't clarify what the issue is. It is obvious that if we convert times to UTC for calculation purposes that this will affect the display of those timestamps, but as far as I can tell, org doesn't convert back and use those converted values in any visible way. Provided all values are converted consistently, it should not matter. Therefore, if there is a problem, then something must not be getting converted correctly, but it is not possible to narrow down where this is without more info. If you can provide an ECM then we can avoid assumptions and different interpretations and focus on the issue. Tim -- Tim Cross