From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: byte-compile-nogroup-warn effectively disabled Date: Mon, 09 Jun 2008 21:17:46 -0400 Message-ID: References: <001901c8c9fc$7b2960b0$0200a8c0@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1213060685 32460 80.91.229.12 (10 Jun 2008 01:18:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Jun 2008 01:18:05 +0000 (UTC) Cc: Drew Adams , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 10 03:18:48 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K5sVb-00027W-0I for ged-emacs-devel@m.gmane.org; Tue, 10 Jun 2008 03:18:47 +0200 Original-Received: from localhost ([127.0.0.1]:45183 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K5sUn-0004WL-2z for ged-emacs-devel@m.gmane.org; Mon, 09 Jun 2008 21:17:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K5sUi-0004UR-At for emacs-devel@gnu.org; Mon, 09 Jun 2008 21:17:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K5sUh-0004Tr-Ni for emacs-devel@gnu.org; Mon, 09 Jun 2008 21:17:51 -0400 Original-Received: from [199.232.76.173] (port=38333 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K5sUh-0004Tf-Km for emacs-devel@gnu.org; Mon, 09 Jun 2008 21:17:51 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:28538) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K5sUd-0006fZ-KS; Mon, 09 Jun 2008 21:17:47 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiMCAGNzTUjO+ISodGdsb2JhbACBW5A0ASeeAg X-IronPort-AV: E=Sophos;i="4.27,615,1204520400"; d="scan'208";a="22344831" Original-Received: from smtp.pppoe.ca (HELO smtp.teksavvy.com) ([65.39.196.238]) by ironport2-out.teksavvy.com with ESMTP; 09 Jun 2008 21:17:47 -0400 Original-Received: from pastel.home ([206.248.132.168]) by smtp.teksavvy.com (Internet Mail Server v1.0) with ESMTP id QHB35147; Mon, 09 Jun 2008 21:17:47 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id C2A0F8265; Mon, 9 Jun 2008 21:17:46 -0400 (EDT) In-Reply-To: (Richard M. Stallman's message of "Mon, 09 Jun 2008 13:22:12 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:98834 Archived-At: > Sorry, I haven't followed this. But IIUYC, I think it would be > a mistake to automatically assign an option or face the group that > was last specified before it in the same file. > What for? What is gained? Sounds like an invitation for user > errors that won't necessarily be noticed right away. It might not > be an important error to assign the wrong group, but why encourage > that possibility? > That is what I feel, too. Omitting the :group is no big savings in > effort; writing it gives you a chance to think about it. I know. And we've already reached the conclusion that we have to agree to disagree on this one. Stefan