From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: What is the best way to set #+DATE to today's date?
Date: Thu, 06 Aug 2015 19:41:33 +0200 [thread overview]
Message-ID: <87si7wl3g2.fsf@gmx.us> (raw)
In-Reply-To: CAFyQvY1AnUKLPvuY1_LON60SZdT6e98JHGpL+eA_jaJRkOcziw@mail.gmail.com
Kaushal <kaushal.modi@gmail.com> writes:
>> Why don't you just use a timestamp?
>
> But that would need me to insert the timestamp manually each time before
> exports
If you *always* want the current date you don't need to set date.
>> You can update whenever you want or using
>> (org-insert-time-stamp (current-time))
>> at the right spot.
>
> Wouldn't that too need manual navigation to #+date: and then eval that
> elisp form?
Sure, but that's easy to find (untested):
(defun rasmus/update-date ()
"update #+date keyword"
(org-with-wide-buffer
(let ((case-fold-search t))
(goto-char (point-min))
(search-forward-regexp "^#+date: ?")
(delete-region (point) (line-end-position))
(org-insert-time-stamp (current-time)))))
My point was that I don't understand the need for your today macro...
Rasmus
--
History is what should never happen again
next prev parent reply other threads:[~2015-08-06 17:41 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 [this message]
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
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=87si7wl3g2.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).