unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>, help-gnu-emacs@gnu.org
Subject: RE: hooks and let-bound variables
Date: Tue, 23 Jun 2015 14:44:17 -0700 (PDT)	[thread overview]
Message-ID: <96506ece-5bd9-4750-8abd-128c77cf6c39@default> (raw)
In-Reply-To: <m2si9i6xtx.fsf@polytechnique.org>

> I’m trying to get eshell-autojump to work but I’m getting
> errors about an undefined variable (curdir). This variable is bound by a
> let before a hook is called:

Yes, but occurrences of that variable in the function called by the hook are not within the lexical scope of that let.

What happens if you add (defvar curdir), to let Emacs know that the variable is to be dynamically scoped?



  reply	other threads:[~2015-06-23 21:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-23 19:15 hooks and let-bound variables Alan Schmitt
2015-06-23 21:44 ` Drew Adams [this message]
2015-06-24  9:13   ` Alan Schmitt
2015-06-24 13:22     ` Drew Adams
2015-06-24 13:35       ` Alan Schmitt
2015-06-24 14:44         ` Drew Adams
2015-06-24 15:48           ` tomas

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=96506ece-5bd9-4750-8abd-128c77cf6c39@default \
    --to=drew.adams@oracle.com \
    --cc=alan.schmitt@polytechnique.org \
    --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).