From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:c151::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id qIaLDvD5hmReyAAASxT56A (envelope-from ) for ; Mon, 12 Jun 2023 12:56:48 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:c151::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id +AIMDfD5hmT14wAAG6o9tA (envelope-from ) for ; Mon, 12 Jun 2023 12:56:48 +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 7ECB763B6 for ; Mon, 12 Jun 2023 12:56:47 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=ZkfeIrA6; 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=1686567408; 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=hlYjj5jJsYRnpLk3bQcaYY/TFa9cnxhyoFNIxKtHOSs=; b=LM1hXiWsZFDVw/CWaJnjwEeUVKN2AMtGcAoUaMcGNagYlAg2e79bp4Jsofd+HYru1ZDuzJ eolYt43xomVkexBrUkwo9HOY9PDVJpYAlmgc8UTa5F39CcpgCgDrq9YtLb9zsRJyW+enkZ CzlqMtLREdHC3A9Va+oM6zIFNmfSsyYYkq3dRdd+tx71tAiOF5ULaRQhmTy6dchFa2qSOz Gxi3/wEVpX8J6JUqhmX5FELj3g5V8EAyJaFQFNT3WQzJjq7irV03nixIb7KznRYclld+S6 hQW01HziqmMvDKnBC0TNwXBqmbRIRNWduN5wG5yNxBifil6ctPi0NRMGWm6k5w== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=ZkfeIrA6; 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-Seal: i=1; s=key1; d=yhetil.org; t=1686567408; a=rsa-sha256; cv=none; b=L9qw7hK5R3iHewm0izfix4k9gAV91IM3PAjyB6/InxjewgdFydIAJi/ZhhOT1/cU8SLKRe gZHMeAmuzaCYam9aibsoGMS9Baw1TZB13qx4xmeoedNVwX9TxDZlYT189M9/mQ2iqoxZ6z x31lpI1QmKleU15O1qanmO8sH/W69SgS1gsAQagSARSd5Itil2kIraA4AVBFaUxrbbGylk 0D1o46BbG9e1rMF3uU9YHcmBfKf1M6zc4o/UdJBV1eKLYdcWdcXI9HwbsPoaTQeyMB/pux J7E9g1KfDu36ald986a/BcDeJDH3H/BURI8MRvamp31MmRYIKiRBDofioWDOFQ== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q8fD8-0005wR-SX; Mon, 12 Jun 2023 06:55:46 -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 1q8fD2-0005w5-Or for emacs-orgmode@gnu.org; Mon, 12 Jun 2023 06:55:40 -0400 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q8fCx-00077S-2o for emacs-orgmode@gnu.org; Mon, 12 Jun 2023 06:55:40 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 6412A240028 for ; Mon, 12 Jun 2023 12:55:33 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1686567333; bh=el1XID0DvN32fk66hVihLU1ydoOPgHgM2+QFOQ3q7fg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=ZkfeIrA6TKRx100gIguj1puTOrCTBqeNbDURMPaFX4gPaojCKCrJ+jx36t5Cwicel W4hwEeN3y8rDAU5RB59jZoUDOovVtnIypLCKxr2IFgTgpcyzj9bP0GpogY+PajN+TO l7BLQ9WsFSctDul/xAPxNVuE1DA1QlQQ3dZBbQhe3a7IOTtFybyZgUcyGDWhFGtBK8 2UuJP5s7bz/ha2yQBWVfYUZdEd5dTV8KOoyMp630mgxWt5j8CXjddVTGt/dagYcFIp f8DN5aGe2r1KkEXD4WKpdfJJy1Y5L2WlAiAcbxIIh14P5bW/nN/kvJ9W4UleJ+Ip+P 5T/MgLXxRghZQ== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4QfpW83XkZz9rxD; Mon, 12 Jun 2023 12:55:32 +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> <875y7y2qga.fsf@localhost> <87h6rh140j.fsf@localhost> <87v8fvtz1u.fsf@localhost> <87a5x6tjr3.fsf@localhost> Date: Mon, 12 Jun 2023 11:00:27 +0000 Message-ID: <87legplzck.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.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: UNKNOWN X-Migadu-Flow: FLOW_IN X-Spam-Score: -5.03 X-Migadu-Queue-Id: 7ECB763B6 X-Migadu-Scanner: in3.migadu.com X-Migadu-Spam-Score: -5.03 X-TUID: HZignuCS+2Bm David Masterson writes: >>> -To assist project planning, TODO items can be labeled with a date >>> -and/or a time. The specially formatted string carrying the date and >>> -time information is called a /timestamp/ in Org mode. >>> +To assist project planning, TODO items can be labeled with dates >>> +and/or times for purposes described in this chapter. The specially >>> +formatted string carrying the date and time information is called a >>> +/timestamp/ in Org mode. >> >> What is the purpose of this change? The updated sentence is rather >> confusing, IMHO. > > Mostly changing the statement from singular to plural to imply that more > than one timestamp can be in a TODO item (SCHEDULED, DEADLINE, multiple > plain timestamps) w/o directly mentioning how (leave that for later > examples in the chapter). I am mostly questioning "for purposes described in this chapter". All the TODO items can be labelled with multiple dates/times, not just in "this chapter". >>> +#+cindex: timestamps >>> +#+cindex: ranges, time >>> +#+cindex: deadlines >>> +#+cindex: scheduling >> >> We do not need cindex and other index keywords in org-guide. > > There are a couple in the diary timestamp section already, but this can > be dropped if wrong. Most likely, they are there by mistake. The guide should be short enough to not require index. >>> +A timestamp is a specification of a date---possibly with a time or a >>> +range of times---in a special format, either =<2003-09-16 Tue>= or >>> +=<2003-09-16 Tue 09:39>= or =<2003-09-16 Tue 12:00-12:30>=. 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/times in the agenda (see [[*The Weekly/Daily Agenda]]). We >>> +distinguish: >> >> This is not accurate. Only date is considered by agenda. Not time. >> Time can be displayed, but has no effect (by default) on whether an >> entry appears in the agenda or not. > > In testing, I found the following: > > * TODO summer school > <2023-06-05 Mon 10:30-12:15>--<2023-06-08 Thu 10:30-12:15> > > ... > Is this being done by an add-on package? I have these, but most of them > are not setup: No. I meant that presence of time has no effect on whether an entry appear in agenda or not. Once agenda decides that an entry should appear, the time is taken into account when formatting the display. You modified the manual to "Its presence causes entries to be shown on specific dates/times in the agenda". There is no concept of "shown on specific time" in agenda views. Just "shown on specific day". >>> - <2006-11-02 Thu 20:00-22:00> >>> + <2006-11-02 Thu 10:00-12:00> >> >> I do not mind, but wondering why you changed the time interval. > > It seemed strange to have a meeting so late at night. ;-) I guess you do not work in academia :) >>> - Timestamp with repeater interval :: >>> >>> A timestamp may contain a /repeater interval/, indicating that it >>> - applies not only on the given date, but again and again after >>> - a certain interval of N days (d), weeks (w), months (m), or years >>> - (y). The following shows up in the agenda every Wednesday: >>> + applies not only on the given date, but again and again after a >>> + certain interval of N hours (h), days (d), weeks (w), months (m), or >>> + years (y). The following shows up in the agenda every week at the >>> + given day of the week and time: >> >> I miss the point here. You changed the last sentence to mention time, >> but the "following" example does not specify the time (<%%(diary-float t 4 2)>). > > I think you're looking at the patch file, so you're not seeing the line > before the 'diary' line which has a time of 22:00-23:00 on it. I don't > use 'diary-float', so did I misinterpret the example? If so, drop the > "and time". The main purpose was to add in "hours" after N. "22:00-23:00" has no relation to timestamps. Agenda still accounts for it because of `org-agenda-search-headline-for-time', but this part of the manual is talking about timestamps, not agenda extras. The diary timestamp does not set the time. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at