From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id sGWbEsetgWRdnwAASxT56A (envelope-from ) for ; Thu, 08 Jun 2023 12:30:31 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id CNSoEcetgWRGWgEAG6o9tA (envelope-from ) for ; Thu, 08 Jun 2023 12:30:31 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id D75343E1ED for ; Thu, 8 Jun 2023 12:30:30 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q7CtS-0007YF-Iy; Thu, 08 Jun 2023 06:29:26 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q7CtQ-0007Y0-0z for emacs-orgmode@gnu.org; Thu, 08 Jun 2023 06:29:24 -0400 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q7CtM-0003nn-Hs for emacs-orgmode@gnu.org; Thu, 08 Jun 2023 06:29:23 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 103D9240104 for ; Thu, 8 Jun 2023 12:29:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1686220158; bh=k4Mx0bI39MGJad6Y8Vp0o74I7HGbtdh4hRyq3y3VT3o=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=YtDmEWijU6laI2cfcMj82384QjDphEX5NRdBxlVh3vjt0cBVGFGtAjAxvIc6bd/sH ofacH0dL+fRPaCp35dhs1Lw5UCG08V7ePr4dFKBy7F6yAy8LUXTfciJcEPm48+7Yb6 sEdWi3pCPsrVmTqmEyvZdqN5Ss/P6M4ReFiiOo+FkAegqUfktX2yjQ1v2un1PAzMvy xsLCCeAkDGWnU7PwXuE4NXETG9ls8/CkgRFBqbFyndk8vH7mmb6red5CM5KXlY4hwW Vc0Uzi8fOmDTYVasEvwdQAaD4a6gGu05Do9KR/dtOgZJintVDTe7WSWa8PfnKwSW2A otC8uK0jZz5bQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QcL6j0w4Rz9rxL; Thu, 8 Jun 2023 12:29:16 +0200 (CEST) From: Ihor Radchenko To: David Masterson Cc: emacs-orgmode@gnu.org Subject: Re: Is this proper time format? In-Reply-To: References: <87r0qplm9y.fsf@localhost> <87ilc1ktrx.fsf@localhost> Date: Thu, 08 Jun 2023 10:33:57 +0000 Message-ID: <875y7y2qga.fsf@localhost> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1686220231; a=rsa-sha256; cv=none; b=JdT+qxbDzvJdo4sr3uOA5oaGxvnFHDEIvVBGK9mCX+vhzniIMqZhAPOHQIugF6gNJ2lctL juFNn3gXCBq8qriUG8WDhbx5Cs4UTuofybnJpeeS4iL9TxD9hkItgmzQQ6oF9nWv5OoIOV euykaynj1Wna/t556SD2S7Eq5Otww1FKyzJHBEemqHMPU43D+JGjj5a6Uojj+UwsozKt+j rUI0KRhbnntiC3wgL2BrpwKgAVwdxubxUrqwc/tbQQRM2ENHHnWHtLD1xYUeZgweLFlMlq /QILaKPIfpY+DjGB06xdEEVMZwSrm6edZfUOOXbged+/YoSKG3x8WhShKHwyCQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=YtDmEWij; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1686220231; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=KXEzHr4VwQIcFQQc+riDo9wxHfy0GwMfHAfhDEzlMak=; b=CNDn72rTPAbSa7QvIrVn9lq/VSQYK98sV0iCAw+zjoHEGX0O8O2GUSxEqEASg0RLqtSdq6 pI9WWx7SQ82Fn7LHEnWVLywUFBstqNwW9lVR9S4Fdg2anOj+LT0deQgfFL/kYm1+wGhhW6 MjUJ5QtYnORfninGI7ahpjqfuI4vN2Zlk/eVhlyXeXDRqbRUu4zFF7L40eU+cYHIcW1z0A NwCZwezbPhI+kQrWOrUtkTmOB96wN0/K5ZP8AkkkxaxIIHDTgLPp6xGzEeYUDsZWyZ8ZvB VUFKMCFqFROJId8NFqFQYM46bT9RTvunFFb0tU6FZv1WaovXM9z4gPpJKiozGw== Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=YtDmEWij; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -7.27 X-Spam-Score: -7.27 X-Migadu-Queue-Id: D75343E1ED X-TUID: 27ha8zTr9WV5 --=-=-= Content-Type: text/plain David Masterson writes: >> AFAIK, closed date intervals with time are currently not supported by >> org-agenda. You can instead use diary sexp timestamps, a bunch of active >> timestamps in the body, or M-x org-clone-subtree-with-time-shift > > "a bunch of active timestamps"?!? Ooh! I hadn't gotten the impression > that that was allowed from the "Dates and Times" section of the manual. > It always talked about "a timestamp" and it made sense to me that a task > would only have one timestamp. Can a statement be added to the manual > to make this explicit? How about the attached patch? --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=0001-doc-org-manual.org-Clarify-how-timestamps-are-consid.patch >From c2e91d5c2c88967b5fb28a077c3c7107a2622334 Mon Sep 17 00:00:00 2001 Message-Id: From: Ihor Radchenko Date: Thu, 8 Jun 2023 13:22:45 +0300 Subject: [PATCH] doc/org-manual.org: Clarify how timestamps are considered by agenda * doc/org-manual.org (Timestamps): Clarify that multiple timestamps may be present under a heading. (Weekly/daily agenda): Add footnote explaining how timestamps are selected when building agenda views. Reported-by: David Masterson Link: https://orgmode.org/list/SJ0PR03MB5455C08FAD47C64F6EA7054CA252A@SJ0PR03MB5455.namprd03.prod.outlook.com --- doc/org-manual.org | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index c11694849..3b54764ab 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -6002,7 +6002,8 @@ ** Timestamps =<2003-09-16 Tue 09:39>=[fn:19]. A timestamp can appear anywhere in the headline or body of an Org tree entry. Its presence causes entries to be shown on specific dates in the agenda (see [[*Weekly/daily -agenda]]). We distinguish: +agenda]]). There can be more than one timestamp in each entry. We +distinguish: - Plain timestamp; Event; Appointment :: @@ -8872,7 +8873,11 @@ *** Weekly/daily agenda #+cindex: daily agenda The purpose of the weekly/daily /agenda/ is to act like a page of -a paper agenda, showing all the tasks for the current week or day. +a paper agenda, showing all the tasks for the current week or day + [fn:: The tasks are displayed according to the contained timestamps. +Agenda has a number of customizations that determine which timestamps +are considered. See =org-agenda-skip= and =org-agenda-daily/weekly= +customization groups for the full list of customizations.]. - {{{kbd(M-x org-agenda a)}}} (~org-agenda-list~) :: -- 2.40.0 --=-=-= Content-Type: text/plain > By closed date interval, I assume you mean "--". That is > mentioned in 8.1 of the manual. It's header is "Time/Date range", but it > only talks about dates (no times) including in the example. Handling of date intervals when TIME1/2 have time specifications is undefined behaviour for now. And I am not in favour of making it defined - we may consider using this semantics to define repeater intervals with end date in future. That would allow what you attempted to do in the original email, but using <2023-06-05 Mon 10:30-12:15>--<2023-06-08 Thu> semantics. See https://orgmode.org/list/877cxp1fbx.fsf@localhost > If times are allowed, then the paragraph could include a time example. > If not, then the header should be changed and "timestamp" should be > changed to "datestamp". No. The same section talks about time range: <2006-11-02 Thu 10:00-12:00> "Timestamp" is the general term we use. We make it explicit in the parent section that timestamps may or may not have time specification: A timestamp is a specification of a date (possibly with a time) in a special format, either =<2003-09-16 Tue>= or =<2003-09-16 Tue 09:39>= -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at --=-=-=--