all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: copyright-update in nnfolder [was Re: Emacs 23.2.94 pretest]
Date: Wed, 16 Feb 2011 11:22:59 +0900	[thread overview]
Message-ID: <87ipwkzpj0.fsf@catnip.gol.com> (raw)
In-Reply-To: <wzr5b9f8a7.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 15 Feb 2011 13:43:28 -0500")

Glenn Morris <rgm@gnu.org> writes:
>> !       (set (make-local-variable 'copyright-update) nil)
>
> I think it would be better for nnfolder just not to do this at all.
> First, how many mail folders happen to contain copyright headers at
> the start?

Sadly, it's all too common for copyright headers to appear in places
that confuse copyright.el; e.g., patch files that update the copyright
(it sees the "from" branch first, so...)!

I presume this sort of very specific workaround wouldn't have been added
to nnfolder unless people had hit

> Second, people should be more selective about enabling features on
> buffer-save. It's not the responsibility of every package that saves a
> buffer to disable every feature (trailing whitespace removal, etc) that
> people might have added to save hooks.

copyright.el, at least, at least _asks_ before doing something, and
rarely actually takes action (because it has fairly narrow criteria for
when an update is needed), so it tends to be just annoying rather than
dangerous (whitespace munging without prompting is downright evil
though).

I agree that there should be a "better" way to do this, but unless there
is, people will continue to do whatever gets the best results on
average; there are annoyances _either_ way.

If there's a convenient way to distinguish "text files" from "other
stuff like mail archives / tar files / ...", then packages like
copyright.el could check that, and ignore any non-text-files...

-miles

-- 
Dawn, n. When men of reason go to bed.



  parent reply	other threads:[~2011-02-16  2:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  4:46 Emacs 23.2.94 pretest Chong Yidong
2011-02-15  4:54 ` Miles Bader
2011-02-15 15:49   ` Chong Yidong
2011-02-15 18:43     ` copyright-update in nnfolder [was Re: Emacs 23.2.94 pretest] Glenn Morris
2011-02-15 20:30       ` Stefan Monnier
2011-02-16  2:22       ` Miles Bader [this message]
2011-02-16 21:28     ` Emacs 23.2.94 pretest Lars Ingebrigtsen
2011-02-17  1:00 ` Sean Sieger
2011-02-23 17:36   ` Uday S Reddy
2011-02-23 17:44     ` Chong Yidong
2011-02-23 17:51       ` Uday S Reddy
2011-02-23 19:01         ` Chong Yidong
2011-02-23 19:27           ` Eli Zaretskii
2011-02-23 20:36           ` Uday S Reddy
2011-02-23 20:41             ` Lennart Borgman
2011-02-24  0:28               ` Christoph
2011-02-23 21:21             ` Chong Yidong
2011-02-23 21:51               ` Eli Zaretskii
2011-02-23 23:11                 ` Chong Yidong
2011-02-23 23:35                   ` Uday Reddy
2011-02-24  3:54                   ` Eli Zaretskii
2011-02-23 23:46               ` Uday S Reddy
2011-02-23 17:59     ` Eli Zaretskii
2011-02-24  1:13       ` Sean Sieger
2011-02-24  4:01         ` Eli Zaretskii
     [not found] ` <4D669A15.9080701@online.de>
2011-02-24 18:09   ` Chong Yidong
2011-02-24 18:56     ` Andreas Schwab
2011-02-24 21:26       ` Andreas Röhler
2011-02-24 22:20         ` Davis Herring
2011-02-25  6:46           ` Andreas Röhler
2011-02-25  9:32             ` Andreas Schwab
2011-02-25 10:09               ` Andreas Röhler
2011-02-25  7:01           ` Andreas Röhler
2011-02-25 13:35             ` Davis Herring
2011-02-25 10:18 ` Andreas Röhler
2011-02-25 10:29   ` Andreas Schwab
2011-02-25 11:31     ` Andreas Röhler
2011-02-25 11:43 ` Andreas Röhler

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=87ipwkzpj0.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@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.
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.