From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: Defaults for elisp-mode files Date: Thu, 4 Oct 2012 19:12:40 +0200 Message-ID: References: <877gr7kory.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1349401940 25150 80.91.229.3 (5 Oct 2012 01:52:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 5 Oct 2012 01:52:20 +0000 (UTC) Cc: emacs-devel@gnu.org To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 05 03:52:23 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TJx4H-0005tv-J2 for ged-emacs-devel@m.gmane.org; Fri, 05 Oct 2012 03:51:09 +0200 Original-Received: from localhost ([::1]:33626 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJozH-0007rZ-2Y for ged-emacs-devel@m.gmane.org; Thu, 04 Oct 2012 13:13:27 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:53441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJozD-0007qc-UP for emacs-devel@gnu.org; Thu, 04 Oct 2012 13:13:24 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TJozB-0000MO-KP for emacs-devel@gnu.org; Thu, 04 Oct 2012 13:13:23 -0400 Original-Received: from mail-wi0-f177.google.com ([209.85.212.177]:64507) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJozB-0000MK-Ds for emacs-devel@gnu.org; Thu, 04 Oct 2012 13:13:21 -0400 Original-Received: by mail-wi0-f177.google.com with SMTP id hj13so849492wib.12 for ; Thu, 04 Oct 2012 10:13:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Cw/9yc4/zektU2QSOyi7jqysafYOhaB0d9vmzqNkGpM=; b=QPc5F3tjG2qwrWLCWi6DyBHotUmb/XmTSornMRwbeiuD5e7B7v3P9Ol/Cw1rVo9pxP sZF3y/JoZjHoxZoaTrhyzWpftgW3lZdSU8VQP7LqV3xK5Dpj5g4sHFYjHBXeVJcnTC3J KzPBTXDs4QvQWPiGPa4BsvZYE75RbXBojGzdOIAhF2bOM9ONCfk36CugWQhZODJZwvXV jyj1rL2xKOlO9LGkXjQUN6hIe0BKdp37Ff5p8hNApZx2EYfQJPcpYvyE7jvt6SKcV6kA AP9Tw6I+q0biNlo6mUOKMosr0b6APo+oLJ+69QMK1WEjFMs4dO6AHO8JQdgJ8nhVUPEo Kx/g== Original-Received: by 10.180.102.131 with SMTP id fo3mr22679257wib.1.1349370800577; Thu, 04 Oct 2012 10:13:20 -0700 (PDT) Original-Received: by 10.223.155.132 with HTTP; Thu, 4 Oct 2012 10:12:40 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.212.177 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:154050 Archived-At: On Thu, Oct 4, 2012 at 7:00 PM, Andreas Schwab wrote: >> variables (byte-compile-dynamic, generated-autoload-file, >> no-byte-compile, no-update-autoloads, lexical-binding itself) through >> the same mechanism. > > You need to make sure that such settings are copied together with the > file when installing it somewhere else. Yes, and no, I think. If you're copying an entire project, presumably you would copy any .dir-locals (or .compilation-whatever-its-name). But, if you're copying an elisp file to fork it or add it to another project, many of these variables could change value easily, even lexical-binding if you're adding it to a back-compatible package. There's nothing really specific to a given elisp file in the assignation of autoload file, or whether update autoloads or not, for example; that's more likely project-specific. Some properties are on the fence, like no-byte-compile (which usually depends more on the size of the file that anything else) . That it's not to say that my idea was particulary good, but if you want, as Stefan wanted, to get rid of marking individually each file for a given property, either you change the default (and resort to marking the hopefully fewer files that so require it), or you add metada externally to the files. Juanma