unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: copyright-update in nnfolder [was Re: Emacs 23.2.94 pretest]
Date: Tue, 15 Feb 2011 13:43:28 -0500	[thread overview]
Message-ID: <wzr5b9f8a7.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87lj1hs3gl.fsf@stupidchicken.com

Chong Yidong wrote:

> *** lisp/gnus/nnfolder.el	2011-01-02 23:50:46 +0000
> --- lisp/gnus/nnfolder.el	2011-02-15 15:47:59 +0000
[...]
> !       (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?
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.



  reply	other threads:[~2011-02-15 18:43 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     ` Glenn Morris [this message]
2011-02-15 20:30       ` copyright-update in nnfolder [was Re: Emacs 23.2.94 pretest] Stefan Monnier
2011-02-16  2:22       ` Miles Bader
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

  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=wzr5b9f8a7.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).