From: Juanma Barranquero <lekktu@gmail.com>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: Emacs Help List <help-gnu-emacs@gnu.org>
Subject: Re: interactive interface to supply variables
Date: Sat, 14 Dec 2013 20:52:59 +0100 [thread overview]
Message-ID: <CAAeL0STFwx3sdnW_pUc0Ne9gb_Peav_iWZj8zmiXUxtyQcHKnQ@mail.gmail.com> (raw)
In-Reply-To: <87vbyr45bj.fsf@nl106-137-194.student.uu.se>
> (symbol-name 'test-var) ; "test-var" (both correct)
This is irrelevant: (symbol-name 'my-var) => "my-var" even if no
(defvar my-var X) was ever used.
> How does `describe-variable' do that? (Perhaps I should
> just copy their interface, because they also suggest
> the variable at point as default. But that's step two.)
custom-variable-p is a compiled Lisp function in `custom.el'.
Return non-nil if variable is a customizable variable.
A customizable variable is either (i) a variable whose property
list contains a non-nil `standard-value' or `custom-autoload'
property, or (ii) an alias for another customizable variable.
So:
(defvar test-var 1)
(put 'test-var 'standard-value t)
J
next prev parent reply other threads:[~2013-12-14 19:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 19:09 interactive interface to supply variables Emanuel Berg
2013-12-14 19:52 ` Juanma Barranquero [this message]
2013-12-15 4:58 ` Michael Heerdegen
[not found] ` <mailman.9280.1387083570.10748.help-gnu-emacs@gnu.org>
2013-12-15 5:23 ` Emanuel Berg
[not found] ` <mailman.9242.1387050824.10748.help-gnu-emacs@gnu.org>
2013-12-14 20:46 ` Emanuel Berg
2013-12-14 21:01 ` Barry Margolin
2013-12-14 21:42 ` Emanuel Berg
2013-12-14 21:09 ` Jambunathan K
[not found] ` <mailman.9258.1387055530.10748.help-gnu-emacs@gnu.org>
2013-12-14 21:46 ` Emanuel Berg
2013-12-14 21:51 ` Emanuel Berg
2013-12-15 5:41 ` Jambunathan K
[not found] ` <mailman.9281.1387086321.10748.help-gnu-emacs@gnu.org>
2013-12-15 18:14 ` Emanuel Berg
2013-12-15 0:09 ` Emanuel Berg
2013-12-15 0:46 ` Emanuel Berg
2013-12-14 23:39 ` 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=CAAeL0STFwx3sdnW_pUc0Ne9gb_Peav_iWZj8zmiXUxtyQcHKnQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=embe8573@student.uu.se \
--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).