From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Is this proper time format?
Date: Thu, 15 Jun 2023 09:04:10 -0700 [thread overview]
Message-ID: <SJ0PR03MB5455A5A7D5C3254EF5C0DEABA25BA@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87h6r9rnkz.fsf@localhost> (Ihor Radchenko's message of "Thu, 15 Jun 2023 11:07:08 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> 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
>> +and/or a time purposes like when an event happens, a deadline for a
>> +task, or tracking time spent on a task as described in later sections
>> +of this chapter. The specially formatted string carrying the date and
>> time information is called a /timestamp/ in Org mode.
>
> What about:
>
> 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. This may be
> a little confusing because timestamp is often used as indicating when
> something was created or last changed. However, in Org mode this term
> is used in a much wider sense.
>
> Timestamps can be used to plan appointments, schedule tasks, set
> deadlines, track time, and more. The following sections describe
> the timestamp format and tooling that Org mode provides for common
> use cases dealing with time and time intervals.
I agree with your change. I'm often minimalist in my changes (especially when
I'm trying not to rock the boat), but that's not always good. If that's
it, make the change in both files and we can call it a day. :-)
--
David Masterson
next prev parent reply other threads:[~2023-06-15 16:10 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
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 [this message]
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=SJ0PR03MB5455A5A7D5C3254EF5C0DEABA25BA@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).