From mboxrd@z Thu Jan 1 00:00:00 1970 From: Allen Li 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: Wed, 1 Nov 2017 21:05:47 -0700 Message-ID: References: <87bmknkwhe.fsf@nicolasgoaziou.fr> <87tvyfjgjk.fsf@nicolasgoaziou.fr> <87tvyelb60.fsf@gmail.com> <87shdykuxc.fsf@gmail.com> <87r2thlewz.fsf@gmail.com> <87o9oll5r8.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44006) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eA6lL-0002o5-88 for emacs-orgmode@gnu.org; Thu, 02 Nov 2017 00:05:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eA6lK-0004WR-6q for emacs-orgmode@gnu.org; Thu, 02 Nov 2017 00:05:51 -0400 Received: from mail-pg0-x22a.google.com ([2607:f8b0:400e:c05::22a]:52750) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eA6lK-0004VD-0J for emacs-orgmode@gnu.org; Thu, 02 Nov 2017 00:05:50 -0400 Received: by mail-pg0-x22a.google.com with SMTP id a192so3944820pge.9 for ; Wed, 01 Nov 2017 21:05:49 -0700 (PDT) In-Reply-To: <87o9oll5r8.fsf@gmail.com> 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: Tim Cross Cc: emacs-orgmode@gnu.org, Nicolas Goaziou On Wed, Nov 1, 2017 at 8:27 PM, Tim Cross wrote: > > 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. It is when doing any kind of tag search. So org-agenda, mostly. I'm not surprised you cannot reproduce it because it is dependent on your local timezone. > > 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. Ah, perhaps I should make the issue clearer. When I run this at 2017-11-01 20:55:30 (org-2ft "") 1509594900.0 (org-2ft "<2017-11-01 20:55:30>") 1509569700.0 Therefore when org.el does a tag search for SCHEDULED="", it will not match <2017-11-01 20:55:30>, assuming that I have frozen my system clock to that time. > > If you can provide an ECM then we can avoid assumptions and different > interpretations and focus on the issue. Again, this is dependent on your local time zone. Try setting your time zone to America/Los_Angeles. 1. emacs -Q 2. Assume it is 2017-10-10 12:00:00 local time 3. Create an agenda file * TODO thing SCHEDULED:<2017-10-10 13:00:00> 4. M-x org-agenda RET m SCHEDULED>"" Expected: thing shows up Actual: thing does not show up > > Tim > > -- > Tim Cross