emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal <kaushal.modi@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: ndokos@gmail.com, emacs-org list <emacs-orgmode@gnu.org>,
	Rasmus <rasmus@gmx.us>, John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: What is the best way to set #+DATE to today's date?
Date: Thu, 6 Aug 2015 15:58:44 -0400	[thread overview]
Message-ID: <CAFyQvY2h9ChhN4Oy8464EbYMOvirVGAgihe8xtsQs4Y6R6_oHw@mail.gmail.com> (raw)
In-Reply-To: <m2bnektcvs.fsf@tsdye.com>

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Yeah, the documentation definitely needs refining.

{{{date}}} / {{{date(FORMAT)}}} [FORMAT is optional] - Inserts the
#+DATE keyword value;
optionally formats as per FORMAT (Refer `format-time-string` function for
syntax.){{{time(FORMAT)}}} - Inserts the current time stamp as per the
FORMAT {{{modification-time(FORMAT)}}} - Inserts modification time of the
file being exported as per the FORMAT


--
Kaushal Modi

On Thu, Aug 6, 2015 at 3:50 PM, Thomas S. Dye <tsd@tsdye.com> wrote:

>
> Kaushal <kaushal.modi@gmail.com> writes:
>
> > Actually the documentation does say what {{{time}}} does; I just didn't
> > read it all this time.
> >
> > {{{date}}}{{{date(FORMAT)}}}{{{time(FORMAT)}}}{{{modification-time(FORMAT
> > )}}}
> > "These macros refer to the #+DATE keyword, *the current date*, and the
> > modification time of the file being exported, respectively."
> >
> > Apologies.
>
> Does it?  I count four macros and three references.  It's not clear to
> me how they map to one another.  How should I read this?
>
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>

[-- Attachment #2: Type: text/html, Size: 3093 bytes --]

  reply	other threads:[~2015-08-06 19:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 16:33 What is the best way to set #+DATE to today's date? Kaushal
2015-08-06 16:44 ` Rasmus
2015-08-06 17:00   ` Kaushal
2015-08-06 17:41     ` Rasmus
2015-08-06 18:18     ` John Kitchin
2015-08-06 19:25       ` Kaushal
2015-08-06 19:45         ` Kaushal
2015-08-06 19:50           ` Thomas S. Dye
2015-08-06 19:58             ` Kaushal [this message]
2015-08-06 20:51               ` [PATCH] " Thomas S. Dye
2015-08-06 21:22                 ` Kaushal
2015-08-06 21:48                   ` Thomas S. Dye
2015-08-06 21:54                     ` Fabrice Niessen
2015-08-06 22:12                       ` Thomas S. Dye
2015-08-07  8:53                         ` Nicolas Goaziou
2015-08-07 14:01                           ` Kaushal
2015-08-07 14:20                             ` Suvayu Ali
2015-08-07 14:52                               ` Kaushal
2015-08-11 18:40                           ` Thomas S. Dye
2015-08-11 22:59                             ` Nicolas Goaziou
2015-08-07  4:31     ` Suvayu Ali
2015-08-06 18:12 ` Nick Dokos

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=CAFyQvY2h9ChhN4Oy8464EbYMOvirVGAgihe8xtsQs4Y6R6_oHw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=ndokos@gmail.com \
    --cc=rasmus@gmx.us \
    --cc=tsd@tsdye.com \
    /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).