From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: parsing time strings from properties
Date: Sat, 21 Sep 2019 16:27:33 -0400 [thread overview]
Message-ID: <CAN_Dec8MJLLQMdOVPxM9bU44CVY0VJF8j=m5VEoXc_numQXy9A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
I use a very simple property in my assignment descriptions to set the
assignment due date:
:DUE_AT: 2019-09-26
I then pass this to an API which expects a date parameter like
`2019-09-26T23:59:59-04:00`. Since I only work in one time zone, I can
just concat the property value with the additional text, though actually I
have to change the `-04:00` string twice a year. I'm wondering though how
hard it would be to get the current time zone -- or the time zone that the
course is taught in -- from emacs, and construct the string from that
value.
Basically, I want a simple date representation to be interpreted as "the
last possible moment on this date i nthe appropriate time zone". I have not
tried to use timestamps here, in part because I'm more comfortable dealing
with text than with the horrors of time representations in either lisp or
javascript. Alsoi, I find it very very fast to insert a text string, and
just a little bit slower and more of an interruption to add a timestamp. I
just wanted to ask how other people manage this kind of operation; maybe I
should make the effort to start using DEADLINE timestamps. I don't really
use them in my own time management so I'm not well-versed in how to manage
them.
In nay case, I as always appreciate all of your help.
Matt
[-- Attachment #2: Type: text/html, Size: 1491 bytes --]
next reply other threads:[~2019-09-21 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 20:27 Matt Price [this message]
2019-09-22 2:54 ` parsing time strings from properties Adam Porter
2019-09-22 10:10 ` Thomas Plass
2019-09-22 17:18 ` Matt Price
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='CAN_Dec8MJLLQMdOVPxM9bU44CVY0VJF8j=m5VEoXc_numQXy9A@mail.gmail.com' \
--to=moptop99@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).