From: Drew Adams <drew.adams@oracle.com>
To: "Alan E. Davis" <lngndvs@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Creating automatic filename stamps
Date: Sat, 24 Nov 2018 08:33:31 -0800 (PST) [thread overview]
Message-ID: <4b455d44-0d2e-4b2b-b738-dd813c96807b@default> (raw)
In-Reply-To: <CAF-1L2TmYNeRa8J=6U40h8YuCcPKACYNtCOc5H2ZSenJ8+GBsw@mail.gmail.com>
> Thank you for that pointer. I haven't gotten far
> in running this down, but I have discovered that
> the file you pointed to is different the another
> time-stamp.el I have in my cache of old *.el files....
Sorry; I don't know more about this than that there
is an Emacs Wiki page that deals with the topic.
You might want to post your questions about it there,
as well. To do that, click "Talk" at the left of
the page footer, and leave a comment with your question.
prev parent reply other threads:[~2018-11-24 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 19:50 Creating automatic filename stamps Alan E. Davis
2018-11-19 20:45 ` Drew Adams
2018-11-24 8:03 ` Alan E. Davis
2018-11-24 16:33 ` Drew Adams [this message]
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=4b455d44-0d2e-4b2b-b738-dd813c96807b@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lngndvs@gmail.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.
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).