From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Document date and last updated date
Date: Tue, 07 Feb 2012 18:45:57 +0100 [thread overview]
Message-ID: <87ty32fsfe.fsf@gmail.com> (raw)
In-Reply-To: <80haz3qavw.fsf_-_@somewhere.org> (Sebastien Vauban's message of "Tue, 07 Feb 2012 09:57:07 +0100")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> Speaking of hyperref and its _document properties_, it makes me think of a
> generic point for which I don't have yet a really satisfactory solution, that
> is about handling dates.
>
> In a PDF document, regarding dates, we have (see output of `pdfinfo'):
>
> - creation date
> - modification date
>
> In Org, we have the `#+DATE:' info keyword, with the date that's supposed to
> be exported onto the final document format (HTML, PDF, OOo, etc.).
>
> But we don't see when the document has been updated for the last time --
> neither when it has been created.
>
> For the former point (date of last update), I've customized Org so that the
> `time-stamp' package updates time stamps every time you save the Org buffer:
>
> #+begin_src emacs-lisp
> (add-hook 'before-save-hook 'time-stamp)
>
> (add-hook 'org-mode-hook
> (lambda ()
> ;; file modification date
> (set (make-local-variable 'time-stamp-format) "%:y-%02m-%02d")
> (set (make-local-variable 'time-stamp-start) "^#\\+DATE: +")
> (set (make-local-variable 'time-stamp-end) "$")))
> #+end_src
>
> That makes my `#+DATE:' info keyword always *up-to-date*.
>
> Though, in some cases:
>
> - I must print a document with a future date (for example, I'm preparing
> slides which I will present on next Monday) -- hence, the above breaks this,
> because I'd like to have next Monday's date already printed on my slides (at
> least on the title page).
>
> - it would be nice to get keep track of the creation date of the Org document,
> though this is not really necessary.
>
> Clearly, I should not make the `#+DATE:' info keyword updated, to keep it for
> its export function (as the official date to be printed on the title page),
> but then it'd be good to have at least a last modification date
> somewhere.
>
> What do you think of all this? How do you do to keep more info on
> dates?
Export systems already provide a {{{modification-time(format-string)}}}
macro by default.
> Some global `draft' or `final' info could make some sense too.
Isn't it too much back-end specific?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-02-07 17:48 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 20:14 [ANN] ASCII back-end for new export engine Nicolas Goaziou
2012-01-21 20:33 ` Samuel Wales
2012-01-21 20:36 ` Samuel Wales
2012-01-21 23:04 ` Nicolas Goaziou
2012-01-22 1:28 ` Samuel Wales
2012-01-22 9:43 ` Nicolas Goaziou
2012-01-22 16:36 ` Samuel Wales
2012-01-28 10:28 ` Samuel Wales
2012-01-28 13:55 ` Nicolas Goaziou
2012-01-28 20:50 ` Samuel Wales
2012-01-28 21:32 ` Nicolas Goaziou
2012-01-28 22:15 ` Samuel Wales
2012-01-28 23:58 ` Nicolas Goaziou
2012-01-22 14:43 ` Martyn Jago
2012-01-22 15:45 ` Nicolas Goaziou
2012-01-22 16:43 ` Martyn Jago
2012-01-23 20:05 ` Eric Schulte
2012-01-23 20:49 ` Nicolas Goaziou
2012-01-22 16:35 ` Thomas S. Dye
2012-01-22 17:10 ` Nicolas Goaziou
2012-01-23 5:58 ` Thomas S. Dye
2012-01-25 17:41 ` Nicolas Goaziou
2012-01-26 6:49 ` Tweaking the export (was: Re: [ANN] ASCII back-end for new export engine) Christian Wittern
2012-01-27 13:06 ` Tweaking the export Nicolas Goaziou
2012-01-27 13:47 ` Jambunathan K
2012-01-27 14:03 ` Sebastien Vauban
2012-01-28 2:33 ` Christian Wittern
2012-01-28 2:21 ` Christian Wittern
2012-01-28 4:03 ` Eric Abrahamsen
2012-01-29 9:07 ` Nicolas Goaziou
2012-02-04 6:21 ` Christian Wittern
2012-02-17 20:06 ` Nicolas Goaziou
2012-01-26 8:44 ` [ANN] ASCII back-end for new export engine Eric S Fraga
2012-01-26 13:59 ` Thomas S. Dye
2012-01-26 15:28 ` Nicolas Goaziou
2012-01-26 17:32 ` Thomas S. Dye
2012-01-26 18:31 ` Nicolas Goaziou
2012-01-26 19:00 ` Achim Gratz
2012-01-27 12:58 ` Nicolas Goaziou
2012-01-27 13:06 ` Rick Frankel
2012-01-27 13:56 ` Nicolas Goaziou
2012-01-27 16:31 ` Achim Gratz
2012-02-01 6:44 ` Achim Gratz
2012-01-26 20:10 ` Thomas S. Dye
2012-02-01 8:36 ` Jambunathan K
2012-01-27 8:10 ` Jambunathan K
2012-01-27 13:59 ` Nicolas Goaziou
2012-01-27 15:50 ` Bastien
2012-01-27 16:29 ` Thomas S. Dye
2012-01-27 17:04 ` Jambunathan K
2012-01-27 18:13 ` Thomas S. Dye
2012-01-27 18:31 ` Jambunathan K
2012-01-27 19:21 ` Achim Gratz
2012-01-27 19:48 ` Thomas S. Dye
2012-01-27 20:10 ` Nick Dokos
2012-01-27 20:11 ` Thomas S. Dye
2012-01-23 21:33 ` Thomas S. Dye
2012-01-22 19:21 ` Thomas S. Dye
2012-01-22 20:50 ` Nicolas Goaziou
2012-01-23 6:14 ` Thomas S. Dye
2012-01-23 7:03 ` Nicolas Goaziou
2012-01-23 15:53 ` Thomas S. Dye
2012-01-23 18:18 ` Nicolas Goaziou
2012-01-23 21:27 ` Thomas S. Dye
2012-01-23 12:20 ` Andreas Leha
2012-01-27 17:00 ` Thomas S. Dye
2012-02-03 22:57 ` Nicolas Goaziou
2012-02-04 16:42 ` Thomas S. Dye
2012-02-05 2:19 ` Thomas S. Dye
2012-02-05 2:58 ` Thomas S. Dye
2012-02-05 14:09 ` Nicolas Goaziou
2012-02-06 1:34 ` Thomas S. Dye
2012-02-06 14:29 ` Nicolas Goaziou
2012-02-06 16:39 ` Thomas S. Dye
2012-02-06 17:05 ` Nicolas Goaziou
2012-02-06 18:46 ` Thomas S. Dye
2012-02-07 7:27 ` Nicolas Goaziou
2012-02-07 8:57 ` Document date and last updated date Sebastien Vauban
2012-02-07 17:45 ` Nicolas Goaziou [this message]
2012-02-07 22:29 ` Sebastien Vauban
2012-02-07 6:22 ` [ANN] ASCII back-end for new export engine Thomas S. Dye
2012-02-07 7:07 ` Nicolas Goaziou
2012-02-07 9:00 ` Sebastien Vauban
2012-02-07 17:49 ` Nicolas Goaziou
2012-02-08 7:11 ` Jambunathan K
2012-02-07 15:45 ` Thomas S. Dye
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=87ty32fsfe.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).