unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: customising a theme?
Date: Sat, 12 Apr 2014 17:37:37 +0200	[thread overview]
Message-ID: <87tx9yd0e6.fsf@web.de> (raw)
In-Reply-To: 87tx9yj2fx.fsf@talktalk.net

Hi Sharon,

    Sharon> During my time working with emacs I have tried many themes
    Sharon> to find my 'ideal theme', which sometimes seems to change
    Sharon> almost everyday. Currently, it is "firebelly", except it has
    Sharon> several shortcomings -

Same for me.  I'm also stuck to it since it appeared in Melpa.

    Sharon>  * when you highlight text, it is unreadable due to it being
    Sharon> the same colour as the background, so it is very hard to
    Sharon> highlight anything.  * TODO items with *** are very
    Sharon> indistinct, so faded that it is almost the same colour as
    Sharon> the background.  * anything that is commented out is
    Sharon> extremely dim and faded, and difficult to read.

    Sharon> I use the following key-bindings to help in choosing and
    Sharon> disabling a theme - (global-set-key (kbd "<f11>")
    Sharon> 'disable-theme) (global-set-key (kbd "<f12>") 'load-theme)

    Sharon> How then can I use this theme with its shortcomings? Is
    Sharon> there a better theme with similar properties?

The readability much depends on your monitor.  For me, everything is
readable, although I find it irritating that variables are even "more
faded" than comments.

Anyway, why don't you just contact the author (the best way would
probably be an github issue)?

About customizing: AFAICT you can't use the customize interface to
customize any custom theme (which makes sense since these themes are
already sets of customizations).

But the defining files are just normal elisp files - in our case,
"firebelly-theme.el".  You can just edit it - it's very easy to read -
or better make your own copy of the theme and put it somewhere in your
`load-path'.


Regards,

Michael.




  reply	other threads:[~2014-04-12 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-12  9:56 customising a theme? Sharon Kimble
2014-04-12 15:37 ` Michael Heerdegen [this message]
2014-04-12 20:41   ` Sharon Kimble
2014-04-13 11:17     ` Michael Heerdegen
2014-04-13 13:56       ` Sharon Kimble
2014-04-13 11:08   ` Michael Heerdegen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87tx9yd0e6.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).