unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ralf Angeli <angeli@caeruleus.net>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Custom themes and simple variables
Date: Fri, 23 Oct 2009 19:05:54 +0200	[thread overview]
Message-ID: <87fx9aoxal.fsf@caeruleus.net> (raw)
In-Reply-To: <87ocny831r.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 23 Oct 2009 12:53:36 -0400")

* Chong Yidong (2009-10-23) writes:

> Ralf Angeli <angeli@caeruleus.net> writes:
>
>> I assume the problem is due to a variable defined with `defvar' not
>> being supported by the Custom machinery, so this is likely not a bug.
>> Would there nevertheless be a possibility to handle such variables
>> cleanly with custom themes?
>
> Any variable that should be supported by Custom (including both
> "vanilla" Custom and Custom themes) ought to be declared with defcustom.
> Is there any reason the variables you are trying to work with are
> `defvar'ed instead?

There is a built-in list of viewers the user can choose from.  And this
list is not supposed to be changed by the user.  Therefore it is
declared with `defvar'.  (The user can add or overwrite viewers in a
separate, customizable variable which is defined with `defcustom'.)

The idea now is that the list of predefined viewers only contains
viewers for the chosen platform.  Per default viewers available on
GNU/Linux would be offered but if a theme for MiKTeX on Windows were
enabled, only viewers available on Windows would be displayed.

-- 
Ralf




  reply	other threads:[~2009-10-23 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 21:11 Custom themes and simple variables Ralf Angeli
2009-10-23 16:53 ` Chong Yidong
2009-10-23 17:05   ` Ralf Angeli [this message]
2009-10-23 17:35     ` Chong Yidong
2009-10-23 17:55       ` Ralf Angeli

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=87fx9aoxal.fsf@caeruleus.net \
    --to=angeli@caeruleus.net \
    --cc=cyd@stupidchicken.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 public inbox

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

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).