From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: GNU Elpa Theme (ahungry-theme) - should I add code to auto load-theme it?
Date: Thu, 05 Feb 2015 19:31:23 +0000 [thread overview]
Message-ID: <87egq4f94k.fsf@violet.siamics.net> (raw)
In-Reply-To: <87mw4sdzi0.fsf@ahungry.com> (Matthew Carter's message of "Thu, 05 Feb 2015 12:44:39 -0500")
>>>>> Matthew Carter <m@ahungry.com> writes:
>>>>> Artur Malabarba <bruce.connor.am@gmail.com> writes:
[…]
>> Users should be able to have multiple themes installed without them
>> all turning on simultaneously.
>> I do agree with need a more intuitive theming experience for new
>> users, but that's a whole other topic.
> When investigating further (and testing with a fresh emacs install) I
> have found that the theme loads without requiring any calls to
> load-theme or modifying the theme load path when installed via ELPA
> by including a simple:
> (require 'ahungry-theme)
> In the init file, so upon reconsideration I'll probably avoid adding
> any further autoload functionality in the theme code.
How is that better than, say, (load-theme 'ahungry t)?
> The fact that the theme becomes active upon a require isn't
> unintended functionality is it?
> Maybe I'll just update the meta description shown on list-packages
> from:
> "Ahungry color theme for Emacs."
> to
> "Ahungry color theme for Emacs - just (require 'ahungry-theme) to
> load."
You can refer to load-theme there just as well, I guess.
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
prev parent reply other threads:[~2015-02-05 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 21:47 GNU Elpa Theme (ahungry-theme) - should I add code to auto load-theme it? Matthew Carter
2015-01-30 21:50 ` 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 [this message]
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=87egq4f94k.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--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.