Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
To: ding@gnus.org
Subject: Re: Update copyright years automatically?
Date: Mon, 03 Jan 2011 10:18:16 +1100	[thread overview]
Message-ID: <87ipy6sxmv.fsf@blah.blah> (raw)
In-Reply-To: <m3wrmnp06h.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 02 Jan 2011 20:36:54 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
> (setq before-save-hook
>       (lambda ()

Supposedly there may be an incompatible change planned in the future to
take away that single func in a hook feature
(http://debbugs.gnu.org/cgi-bin/bugreport.cgi?bug=5026)

> 	(when (string-match "gnus/lisp/.*.el\\'" (buffer-file-name))
> 	  (copyright-update))))

I never found a clean way to express what should or shouldn't be
updated.

> It's kinda annoying that `copyright-update' queries me when saving, though.

Maybe `copyright-query'.  I'd like it to show the buffer and highlight
the change it's about to make, like a query-replace, since occasionally
it's wrong.



  reply	other threads:[~2011-01-02 23:18 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
2011-01-02 23:18     ` Kevin Ryde [this message]
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=87ipy6sxmv.fsf@blah.blah \
    --to=user42@zip.com.au \
    --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).