Ihor Radchenko <yanta...@posteo.net> writes: > David Masterson <dsmaster...@gmail.com> 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). >> ** Timestamps >> :PROPERTIES: >> :DESCRIPTION: Assigning a time to a tree entry. >> :END: >> +#+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. >> -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 in >> -the agenda (see [[*The Weekly/Daily Agenda]]). We distinguish: >> +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> This shows in my timegrid agenda for the week for Mon, Tue, Wed, & Thu on the specified time range. Interestingly, each agenda item had a "(n/4)" on it (n=1 to 4). Also, if you mark any of the 4 as DONE, then all change to DONE (which you kind of expect for this style). Is this being done by an add-on package? I have these, but most of them are not setup: org-ac-20170401.1307 org-books-20210408.1913 org-brain-20230217.1908 org-contacts-1.1 org-download-20220906.1929 org-edna-1.1.2 org-emms-20230515.1838 org-noter-20230605.323 org-noter-pdftools-20220320.300 org-pdftools-20220320.301 org-ql-20230525.1548 org-super-agenda-20220826.2315 org-vcard-20221111.328 >> - <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. ;-) >> - 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. -- David Masterson
