From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thierry Volpiatto Newsgroups: gmane.emacs.devel Subject: Re: Possible defvar bug Date: Mon, 18 Feb 2013 17:26:28 +0100 Organization: Emacs Helm Message-ID: <87wqu5k2q3.fsf@gmail.com> References: <87d2vxr8h6.fsf@thinkpad.tsdh.de> <87obfhy8zc.fsf@gmail.com> <20130218150954.GA4583@acm.acm> <8738wty6hz.fsf@gmail.com> <340816FB6EB446BFBBCCCA6551E851E9@us.oracle.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1361204812 15812 80.91.229.3 (18 Feb 2013 16:26:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 18 Feb 2013 16:26:52 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 18 17:27:15 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1U7TYf-0004QB-7m for ged-emacs-devel@m.gmane.org; Mon, 18 Feb 2013 17:27:13 +0100 Original-Received: from localhost ([::1]:33233 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U7TYL-0007W7-8P for ged-emacs-devel@m.gmane.org; Mon, 18 Feb 2013 11:26:53 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:43384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U7TYD-0007V3-UX for emacs-devel@gnu.org; Mon, 18 Feb 2013 11:26:51 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U7TYC-0007fp-Ab for emacs-devel@gnu.org; Mon, 18 Feb 2013 11:26:45 -0500 Original-Received: from mail-wg0-f45.google.com ([74.125.82.45]:33017) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U7TYC-0007fW-5N for emacs-devel@gnu.org; Mon, 18 Feb 2013 11:26:44 -0500 Original-Received: by mail-wg0-f45.google.com with SMTP id dq12so4888697wgb.24 for ; Mon, 18 Feb 2013 08:26:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:organization:references:date :in-reply-to:message-id:user-agent:mime-version:content-type; bh=8tpxFQOd9e97agTVoAIeeM2AuE6e90aX3OVfQZFE60I=; b=XlvCdKaSiV9Tg5QU5IrnzGpBVC+mnEoOTkir9xk++uiVKPVsSvYSpJYlfZHog/60oG RcM5aW/Ixlm3JVCjPVRS7l3ITg94hnQIaMjvhNWy4aDfkgq2CKl5U1dzbCIi3+mAHCTz d8HeoZAxdqZXS/aSBVN/IA/kBysmHf5MJQimfDTzVL2Cu7bagKI0yH9Fs+DozbO0Jfra b6y0Hm4bbSgJYFhqCkQhUD65kd8Icu7g6gBcZ/xxBDqTOsy9dhwA8pUeMMsFO38sIJ9B myH6ddE5iaasLYDG37wdoDuC8TC7075tZliod14YhPgvhwzZ99qmfomxOZoUXhINUOkK fJrw== X-Received: by 10.180.92.39 with SMTP id cj7mr21500952wib.19.1361204797676; Mon, 18 Feb 2013 08:26:37 -0800 (PST) Original-Received: from dell-14z (lbe83-2-78-243-104-167.fbx.proxad.net. [78.243.104.167]) by mx.google.com with ESMTPS id n10sm22666791wia.0.2013.02.18.08.26.35 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 18 Feb 2013 08:26:36 -0800 (PST) In-Reply-To: <340816FB6EB446BFBBCCCA6551E851E9@us.oracle.com> (Drew Adams's message of "Mon, 18 Feb 2013 08:15:35 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 74.125.82.45 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:157136 Archived-At: "Drew Adams" writes: >> See also documentation of `require' which should not be used inside >> `let' bindings for same reasons. > > Hm. What doc of `require' mentions this? ,---- | The expression `(require 'comint)' loads the file `comint.el' if it has | not yet been loaded, ensuring that `comint-dynamic-complete-filename' | is defined. Features are normally named after the files that provide | them, so that `require' need not be given the file name. (Note that it | is important that the `require' statement be outside the body of the | `let'. Loading a library while its variables are let-bound can have | unintended consequences, namely the variables becoming unbound after | the let exits.) `---- > 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? Of course. -- Thierry Get my Gnupg key: gpg --keyserver pgp.mit.edu --recv-keys 59F29997