From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Possible defvar bug
Date: Mon, 18 Feb 2013 20:17:35 +0530 [thread overview]
Message-ID: <87obfhy8zc.fsf@gmail.com> (raw)
In-Reply-To: <87d2vxr8h6.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Mon, 18 Feb 2013 15:40:21 +0100")
The documentation of `defvar' has the following paragraphs. I am
certain I don't understand what these paragraphs mean, particularly the
second one. Just throwing my hat, to see where it lands.
,---- C-h f
| The optional argument INITVALUE is evaluated, and used to set SYMBOL,
| only if SYMBOL's value is void. If SYMBOL is buffer-local, its
| default value is what is set; buffer-local values are not affected.
| If INITVALUE is missing, SYMBOL's value is not set.
|
| If SYMBOL has a local binding, then this form affects the local
| binding. This is usually not what you want. Thus, if you need to
| load a file defining variables, with this form or with `defconst' or
| `defcustom', you should always load that file _outside_ any bindings
| for these variables. (`defconst' and `defcustom' behave similarly in
| this respect.)
`----
Tassilo Horn <tsdh@gnu.org> writes:
> Hi all,
>
> I have a problem in AUCTeX where I get some void-variable error although
> I require the file defining the variable. After some experimenting,
> I've isolated the problem to this minimal example:
>
> (let ((crm-separator ","))
> (require 'crm))
>
> crm.el defines `crm-separator' with some default value. However, when
> evaluating that snipped, I get:
>
> ,----[ C-h v crm-separator ]
> | crm-separator is a variable defined in `crm.el'.
> | It is void as a variable.
> |
> | Documentation:
> | Separator regexp used for separating strings in `completing-read-multiple'.
> | It should be a regexp that does not match the list of completion candidates.
> | Modify this value to make `completing-read-multiple' use a separator other
> | than `crm-default-separator'.
> `----
>
> I understand that defvar doesn't override a variable's value if the
> variable is already defined, but is that TRT with dynamic bindings, too?
>
> Bye,
> Tassilo
>
>
--
next prev parent reply other threads:[~2013-02-18 14:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 14:40 Possible defvar bug Tassilo Horn
2013-02-18 14:47 ` Jambunathan K [this message]
2013-02-18 14:58 ` Tassilo Horn
2013-02-18 15:00 ` Didier Verna
2013-02-18 15:09 ` Alan Mackenzie
2013-02-18 15:41 ` Thierry Volpiatto
2013-02-18 16:15 ` Drew Adams
2013-02-18 16:26 ` Thierry Volpiatto
2013-02-18 16:40 ` Drew Adams
2013-02-18 16:29 ` Lawrence Mitchell
2013-02-18 15:42 ` Tassilo Horn
2013-02-18 16:19 ` Didier Verna
2013-02-19 1:40 ` Glenn Morris
2013-02-19 15:25 ` Richard Stallman
2013-02-19 17:28 ` Stefan Monnier
2013-02-19 23:29 ` Richard Stallman
2013-02-20 0:08 ` Stefan Monnier
2013-02-20 8:09 ` Tassilo Horn
2013-02-20 14:05 ` Stefan Monnier
2013-02-20 21:36 ` Richard Stallman
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=87obfhy8zc.fsf@gmail.com \
--to=kjambunathan@gmail.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).