unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17996@debbugs.gnu.org
Subject: bug#17996: 24.4.50; `theme-value' in (elisp) `Standard Properties', `Variable Definitions'
Date: Sat, 03 Aug 2019 22:24:20 +0200	[thread overview]
Message-ID: <87o916c80b.fsf@mouse.gnus.org> (raw)
In-Reply-To: <e4032666-84f0-4e86-9486-6d236cfc8bc5@default> (Drew Adams's message of "Fri, 11 Jul 2014 07:50:58 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> Node Standard Properties says this:
>
>  `customized-value'
>  `saved-value'
>  `standard-value'
>  `theme-value'
>       These properties are used to record a customizable variable's
>       standard value, saved value, customized-but-unsaved value, and
>       themed values.  Do not set them directly; they are managed by
>       `defcustom' and related functions.  *Note Variable Definitions::.
>
> But node Variable Definitions says nothing about `theme-value'.  There
> is no explanation of it in the manual.  Seems like an oversight by
> whoever added `theme-value' to this list.
>
> Please document `theme-value', at least to the degree that the others
> are documented.  Perhaps the proper place to document it would be node
> `Custom Themes'.  (And then correct the cross reference for it in node
> Standard Properties.)

I put it in the "Variable Definition" node, and linked to the theme node.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-08-03 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11 14:50 bug#17996: 24.4.50; `theme-value' in (elisp) `Standard Properties', `Variable Definitions' Drew Adams
2019-08-03 20:24 ` Lars Ingebrigtsen [this message]
2019-08-03 21:13   ` Drew Adams

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=87o916c80b.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=17996@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).