From: Rick <rick.stanley.inc@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Using hhmts Timestamp in a <meta> tag, Feature Request
Date: Tue, 17 Mar 2009 11:26:16 -0700 (PDT) [thread overview]
Message-ID: <c5869957-ae43-4bd0-9333-bcbe59d0f151@j39g2000yqn.googlegroups.com> (raw)
In-Reply-To: 87tz5swnne.fsf@usenet.my.skamphausen.de
On Mar 17, 4:37 am, Stefan Kamphausen <ska...@gmx.net> wrote:
> Hi,
>
> I'd drop the hhmts-tags and switch to time-stamp.
>
> Put something like this into your emacs-init-file:
> (require 'time-stamp)
> (add-hook 'write-file-hooks 'time-stamp)
...
Actually, I found I had to use:
(add-hook 'before-save-hook 'time-stamp)
instead to make it work.
(Debian Emacs 22.2.1)
Thanks again for pointing this out to me!
Cheers!
Rick
next prev parent reply other threads:[~2009-03-17 18:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ee7f666a-96f6-445f-9d21-85dee25e15b2@c11g2000yqj.googlegroups.com>
2009-03-17 8:37 ` Using hhmts Timestamp in a <meta> tag, Feature Request Stefan Kamphausen
2009-03-17 16:23 ` Rick
2009-03-17 18:26 ` Rick [this message]
2009-03-16 22:04 Rick
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c5869957-ae43-4bd0-9333-bcbe59d0f151@j39g2000yqn.googlegroups.com \
--to=rick.stanley.inc@gmail.com \
--cc=help-gnu-emacs@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.
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).