emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Tue, 06 Jun 2023 06:08:02 +0000	[thread overview]
Message-ID: <87ilc1ktrx.fsf@localhost> (raw)
In-Reply-To: <SJ0PR03MB545568CDA7AB951C8141A834A24DA@SJ0PR03MB5455.namprd03.prod.outlook.com>

David Masterson <dsmasterson@gmail.com> writes:

> Hmm.  What about this:
>
>       <2023-06-05 Mon>--<2023-06-08 Thu 10:30-12:15>
>
> Is there a recommended specification for my meeting?  Or do I have to
> break it into multiple tasks (one for each day)?

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

> Anyone know how well BeOrg, Orgzly, and Organice handle this?

No idea.

-- 
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>


  reply	other threads:[~2023-06-06  6:03 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 [this message]
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
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=87ilc1ktrx.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).