From: Ihor Radchenko <yantar92@posteo.net>
To: David Masterson <dsmasterson@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Is this proper time format?
Date: Mon, 12 Jun 2023 11:00:27 +0000 [thread overview]
Message-ID: <87legplzck.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB5455E2524BD6FEE8EBC3E8E2A254A@SJ0PR03MB5455.namprd03.prod.outlook.com>
David Masterson <dsmasterson@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).
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 <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-06-12 10:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 16:58 Is this proper time format? David Masterson
2023-06-05 19:52 ` Ihor Radchenko
2023-06-05 21:03 ` David Masterson
2023-06-06 6:08 ` Ihor Radchenko
2023-06-06 18:01 ` David Masterson
2023-06-06 23:52 ` Samuel Wales
2023-06-07 5:40 ` David Masterson
2023-06-08 10:33 ` Ihor Radchenko
2023-06-08 23:09 ` David Masterson
2023-06-09 7:36 ` Ihor Radchenko
2023-06-10 2:34 ` David Masterson
2023-06-10 10:02 ` Ihor Radchenko
2023-06-11 0:01 ` David Masterson
2023-06-11 9:31 ` Ihor Radchenko
2023-06-12 0:19 ` David Masterson
2023-06-12 10:44 ` Ihor Radchenko
2023-06-11 6:20 ` David Masterson
2023-06-11 9:45 ` Ihor Radchenko
2023-06-12 0:16 ` David Masterson
2023-06-12 11:00 ` Ihor Radchenko [this message]
2023-06-12 18:02 ` David Masterson
2023-06-13 9:41 ` Ihor Radchenko
2023-06-14 6:16 ` David Masterson
2023-06-14 11:01 ` Ihor Radchenko
2023-06-15 3:35 ` David Masterson
2023-06-15 11:07 ` Ihor Radchenko
2023-06-15 16:04 ` David Masterson
2023-06-16 9:38 ` Ihor Radchenko
2023-06-17 0:54 ` David Masterson
2023-06-17 12:33 ` Ihor Radchenko
2023-06-18 3:57 ` David Masterson
2023-06-18 10:42 ` Ihor Radchenko
2023-06-18 19:05 ` David Masterson
2023-06-18 20:53 ` Ihor Radchenko
2023-06-19 18:13 ` David Masterson
2023-06-10 2:40 ` David Masterson
2023-06-23 12:18 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87legplzck.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).