all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matthew Carter <m@ahungry.com>
To: emacs-devel@gnu.org
Subject: GNU Elpa Theme (ahungry-theme) - should I add code to auto load-theme it?
Date: Fri, 30 Jan 2015 16:47:39 -0500	[thread overview]
Message-ID: <87iofo7xfo.fsf@ahungry.com> (raw)

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



             reply	other threads:[~2015-01-30 21:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 21:47 Matthew Carter [this message]
2015-01-30 21:50 ` GNU Elpa Theme (ahungry-theme) - should I add code to auto load-theme it? Dmitry Gutov
2015-01-30 23:57 ` Artur Malabarba
2015-02-05 17:44   ` Matthew Carter
2015-02-05 19:13     ` Stefan Monnier
2015-02-05 19:58       ` Matthew Carter
2015-02-05 20:48         ` Stefan Monnier
2015-02-05 22:08         ` Artur Malabarba
2015-02-06  4:03           ` Matthew Carter
2015-02-06  8:59             ` Artur Malabarba
2015-02-05 19:31     ` Ivan Shmakov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iofo7xfo.fsf@ahungry.com \
    --to=m@ahungry.com \
    --cc=emacs-devel@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.