From: Lennart Borgman <lennart.borgman@gmail.com>
To: Kevin Rodgers <kevin.d.rodgers@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How can url-show-status be void when (featurep 'url-vars) is t?
Date: Tue, 29 Jun 2010 11:51:53 +0200 [thread overview]
Message-ID: <AANLkTilc63KWBbvIT4XjLdP1S_nyhWheiuGnTs33TCq7@mail.gmail.com> (raw)
In-Reply-To: <i0c1ai$paa$1@dough.gmane.org>
On Tue, Jun 29, 2010 at 7:45 AM, Kevin Rodgers
<kevin.d.rodgers@gmail.com> wrote:
> Lennart Borgman wrote:
>>
>> On Sun, Jun 27, 2010 at 8:08 PM, Andreas Schwab <schwab@linux-m68k.org>
>> wrote:
>>>
>>> Lennart Borgman <lennart.borgman@gmail.com> writes:
>>>
>>>> Any ideas how then url-show-status can be void after loading url-vars?
>>>
>>> ELISP> (let (url-show-status) (load "url-vars"))
>>> t
>>> ELISP> (boundp 'url-show-status)
>>> nil
>>
>> Ah, thanks. I managed to move (require 'url-vars) inside the let-clause.
>>
>> That is pretty easy to do when you are restructuring something. I did
>> not notice until many months later so I had forgotten about the change
>> of course.
>
>> Wouldn't it be possible for defvar, defcustom etc to detect that
>> situation?
>
> defvar does this:
>
> { /* Check if there is really a global binding rather than just a let
> binding that shadows the global unboundness of the var. */
> volatile struct specbinding *pdl = specpdl_ptr;
> while (--pdl >= specpdl)
> {
> if (EQ (pdl->symbol, sym) && !pdl->func
> && EQ (pdl->old_value, Qunbound))
> {
> message_with_string ("Warning: defvar ignored because %s is
> let-bound",
> SYMBOL_NAME (sym), 1);
> break;
> }
> }
> }
Thanks, but should not that be an error?
next prev parent reply other threads:[~2010-06-29 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 0:32 How can url-show-status be void when (featurep 'url-vars) is t? Lennart Borgman
2010-06-27 18:08 ` Andreas Schwab
2010-06-27 22:06 ` Lennart Borgman
2010-06-29 5:45 ` Kevin Rodgers
2010-06-29 9:51 ` Lennart Borgman [this message]
2010-07-01 0:43 ` Stefan Monnier
2010-07-01 6:21 ` David Kastrup
2010-06-27 18:13 ` Chong Yidong
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=AANLkTilc63KWBbvIT4XjLdP1S_nyhWheiuGnTs33TCq7@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kevin.d.rodgers@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 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).