From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Update copyright years automatically?
Date: Sun, 02 Jan 2011 20:36:54 +0100 [thread overview]
Message-ID: <m3wrmnp06h.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m2sjxb5sb9.fsf@igel.home>
Andreas Schwab <schwab@linux-m68k.org> writes:
> (add-hook 'write-file-functions 'copyright-update)
I did
(setq before-save-hook
(lambda ()
(when (string-match "gnus/lisp/.*.el\\'" (buffer-file-name))
(copyright-update))))
to avoid having that happen other places.
It's kinda annoying that `copyright-update' queries me when saving, though.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-02 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 5:26 Lars Magne Ingebrigtsen
2011-01-02 13:49 ` Andreas Schwab
2011-01-02 19:36 ` Lars Magne Ingebrigtsen [this message]
2011-01-02 23:18 ` Kevin Ryde
2011-01-02 23:48 ` Lars Magne Ingebrigtsen
2011-01-03 1:01 ` Kevin Ryde
2011-01-03 4:43 ` Lars Magne Ingebrigtsen
2011-01-03 4:55 ` Lars Magne Ingebrigtsen
2011-01-10 22:32 ` Kevin Ryde
2011-01-10 23:29 ` Russ Allbery
2011-01-11 18:48 ` Lars Magne Ingebrigtsen
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=m3wrmnp06h.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.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 NNTP newsgroup(s).