From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Matthew Carter Newsgroups: gmane.emacs.devel Subject: GNU Elpa Theme (ahungry-theme) - should I add code to auto load-theme it? Date: Fri, 30 Jan 2015 16:47:39 -0500 Organization: Ahungry (http://ahungry.com) Message-ID: <87iofo7xfo.fsf@ahungry.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1422654482 28421 80.91.229.3 (30 Jan 2015 21:48:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 Jan 2015 21:48:02 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 30 22:48:01 2015 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 1YHJPy-0007Kz-0d for ged-emacs-devel@m.gmane.org; Fri, 30 Jan 2015 22:47:58 +0100 Original-Received: from localhost ([::1]:38881 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHJPx-0006s4-Bk for ged-emacs-devel@m.gmane.org; Fri, 30 Jan 2015 16:47:57 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38098) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHJPk-0006ry-OA for emacs-devel@gnu.org; Fri, 30 Jan 2015 16:47:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YHJPh-0006LH-EB for emacs-devel@gnu.org; Fri, 30 Jan 2015 16:47:44 -0500 Original-Received: from li130-200.members.linode.com ([69.164.215.200]:33533 helo=mail.ahungry.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHJPh-0006LB-Ae for emacs-devel@gnu.org; Fri, 30 Jan 2015 16:47:41 -0500 Original-Received: from Prometheus (99-40-9-245.lightspeed.livnmi.sbcglobal.net [99.40.9.245]) by mail.ahungry.com (Postfix) with ESMTPSA id 88EE2407E for ; Fri, 30 Jan 2015 16:47:40 -0500 (EST) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 69.164.215.200 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:182099 Archived-At: Currently it works as expected in GNU Elpa (for installing), however it requires the user to include something like this in their init: (add-to-list 'custom-theme-load-path "~/.emacs.d/elpa/ahungry-theme-1.0.3/") (load-theme 'ahungry t) Which isn't as bad when they had to explicitly install it from my github, as they were sure to read the README and see those lines are required to be manually entered. With an install via GNU Elpa though, I think that directory is going to be changing with the version number of the package, so it would require constant updates to the user's init. Should I update the package to do some or all of the following? (or would the theme be too aggressive if so): 1) Add itself to the user's custom-theme-load-path 2) Load itself via load-theme If either, anyone have a suggestion? I see Elpa packages have an autoload file generated which adds the package to the load-path - is there a package meta tag/comment to do the same for custom-theme-load-path? I personally would expect a theme I pulled in via package-install to at least do #1, and if I were new to emacs, I'd probably expect it to do #2 as well. -- Matthew Carter (m@ahungry.com) http://ahungry.com