From: Antoine Levitt <antoine.levitt@gmail.com>
To: 9583@debbugs.gnu.org
Subject: bug#9583: 24.0.50; erc button-next-function assumes lexical binding invalidly
Date: Fri, 23 Sep 2011 08:40:03 +0200 [thread overview]
Message-ID: <87boub92yk.fsf@gmail.com> (raw)
In-Reply-To: <4E7BFACF.2050303@umn.edu>
23/09/11 05:19, Evan Izaksonas-Smith
> Start Emacs however you like, go to any location in the buffer besided
> the input line and hit TAB. The message: "completion-at-point: Symbol's
> value as variable is void: here" will appear. this is solved by
> changing line 433 from
>
> (let ((here (point)))
> to
> (lexical-let ((here (point)))
Yes, see also bug #9487. This solution is more elegant than the one
posted there. Someone please apply this.
prev parent reply other threads:[~2011-09-23 6:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 3:19 bug#9583: 24.0.50; erc button-next-function assumes lexical binding invalidly Evan Izaksonas-Smith
2011-09-23 6:40 ` Antoine Levitt [this message]
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=87boub92yk.fsf@gmail.com \
--to=antoine.levitt@gmail.com \
--cc=9583@debbugs.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).