all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Thierry Volpiatto'" <thierry.volpiatto@gmail.com>,
	<emacs-devel@gnu.org>
Subject: RE: Possible defvar bug
Date: Mon, 18 Feb 2013 08:15:35 -0800	[thread overview]
Message-ID: <340816FB6EB446BFBBCCCA6551E851E9@us.oracle.com> (raw)
In-Reply-To: <8738wty6hz.fsf@gmail.com>

> See also documentation of `require' which should not be used inside
> `let' bindings for same reasons.

Hm.  What doc of `require' mentions this?  I looked at the doc string and
(elisp) `Named Features', but I didn't notice anything about this.

I hope that the doc for this, wherever it might be, is more specific than what
you said, because I cannot imagine that such a blanket statement is correct.
Presumably, any potential problem would depend on what variables the `let'
binds?




  reply	other threads:[~2013-02-18 16:15 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=340816FB6EB446BFBBCCCA6551E851E9@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=thierry.volpiatto@gmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.