From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [PATCH] Add "Time-stamp: <>" in (first 8 lines of) export template
Date: Tue, 20 Mar 2012 13:45:43 +0100 [thread overview]
Message-ID: <80ehsn1lvs.fsf@somewhere.org> (raw)
In-Reply-To: 87limvo5ki.fsf@gnu.org
Hi Bastien,
Bastien wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>
>>From 74f376c12cceae196f5a856eac1a39cdbcc8e360 Mon Sep 17 00:00:00 2001
>> From: Sebastien Vauban <sva-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
>> Date: Thu, 16 Feb 2012 15:48:37 +0100
>> Subject: [PATCH] Add Time-stamp in export template
>>
>> ---
>> lisp/org-exp.el | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> I'm not applying this patch.
>
> I see how it can be useful for those who use
>
> (add-hook 'before-save-hook 'time-stamp)
>
> but #+Time-stamp is *not* an Org option... so unless we find
> a way to use it without confusing the user, I won't apply it.
OK, so what about adding it as an Org option?
Even if, by default, it must be capitalized as in the example, I can make it
become case-insensitive, so that `#+time-stamp', `#+Time-stamp' and
`#+TIME-STAMP' all are accepted.
Then, I can provide a patch with `time-stamp' function added to
`before-save-hook' in Org mode.
> If you have another proposal, please provide a commit message
> with your patch!
I'll do.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-03-20 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 15:01 [PATCH] Add "Time-stamp: <>" in (first 8 lines of) export template Sebastien Vauban
2012-03-20 11:49 ` Bastien
2012-03-20 12:45 ` Sebastien Vauban [this message]
2012-03-20 15:58 ` Brian Wightman
2012-03-23 14:10 ` Bastien
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=80ehsn1lvs.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.