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: Feature Request: Per-package custom save files? Date: Mon, 23 Jun 2014 21:24:14 -0400 Message-ID: References: <21413.43005.992475.896234@lapdog.roam.corp.google.com> <21416.23354.391473.953888@retriever.mtv.corp.google.com> <21416.39268.648625.775759@retriever.mtv.corp.google.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1403573083 6018 80.91.229.3 (24 Jun 2014 01:24:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Jun 2014 01:24:43 +0000 (UTC) Cc: tv.raman.tv@gmail.com, emacs-devel@gnu.org To: raman@google.com (T.V Raman) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 24 03:24:36 2014 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 1WzFTN-0008KW-Jl for ged-emacs-devel@m.gmane.org; Tue, 24 Jun 2014 03:24:33 +0200 Original-Received: from localhost ([::1]:56985 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzFTN-0005wQ-2Y for ged-emacs-devel@m.gmane.org; Mon, 23 Jun 2014 21:24:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzFTD-0005wI-8I for emacs-devel@gnu.org; Mon, 23 Jun 2014 21:24:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WzFT5-00019U-O1 for emacs-devel@gnu.org; Mon, 23 Jun 2014 21:24:23 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:12464) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WzFT5-00019I-KJ for emacs-devel@gnu.org; Mon, 23 Jun 2014 21:24:15 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArUGAIDvNVNLd+D9/2dsb2JhbABZgwaDSsA9gRcXdIIlAQEBAQIBViMFCws0EhQYDVCHWAjSGReOegeEOASUYwWUMYFqg0wh X-IPAS-Result: ArUGAIDvNVNLd+D9/2dsb2JhbABZgwaDSsA9gRcXdIIlAQEBAQIBViMFCws0EhQYDVCHWAjSGReOegeEOASUYwWUMYFqg0wh X-IronPort-AV: E=Sophos;i="4.97,753,1389762000"; d="scan'208";a="69322622" Original-Received: from 75-119-224-253.dsl.teksavvy.com (HELO pastel.home) ([75.119.224.253]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 23 Jun 2014 21:24:14 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 605E8603CD; Mon, 23 Jun 2014 21:24:14 -0400 (EDT) In-Reply-To: <21416.39268.648625.775759@retriever.mtv.corp.google.com> (T. V. Raman's message of "Mon, 23 Jun 2014 14:17:24 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 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:172672 Archived-At: > What I'm mostly looking for is to have a modular collection of > custom files -- note -- here I'm explicitly talking about > customizations for add-on packages -- not for built-ins. That's still not very clear. For example, we could split the customization "by package" (more or less) while still loading all the customizations at startup. So it would satisfy your above requirement, but not the requirement you sent earlier (quoted below). And it's still not clear how that would change your life, as an Emacs user. Again, I'm not arguing against it, really, but there are many ways to "do it" with very different results, and some answers may correspond to one of your descriptions yet might fail to really solve your problem. So, if you could give us an example of a concrete problem you face, that would help. E.g. "loading my customization file takes too long". Or "I get lost in my customize-changed". Or "I share my customization between different systems but some customizations are system-specific so I don't want to share those". ... Stefan > Stefan Monnier writes: >> > 2. My thought around factoring out custom settings into a >> > canonical per-package custom-settings file was to achieve the >> > second goal -- not loading settings for packages you dont use -- >> >> That doesn't really sound like a goal to me. More specifically, I'd >> like to know why you care about loading settings you don't use. >> >> IOW, let's imagine we change it so that the settings are only loaded >> once they're needed. How will you tell the difference? >> >> >> Stefan