From: Deokhwan Kim <deokhwankim@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Surrounding Lexical Variable Reference in the Body of defun
Date: Thu, 23 Aug 2012 05:52:05 -0700 (PDT) [thread overview]
Message-ID: <980a4157-dd9f-46c7-8564-3eeb8b8fbc3c@googlegroups.com> (raw)
In-Reply-To: <jwvtxvvvucc.fsf-monnier+gnu.emacs.help@gnu.org>
For reference, Revision 108427 (especially, lisp/emacs-lisp/byte-run.el) looks like bringing that change:
http://bzr.savannah.gnu.org/lh/emacs/trunk/revision/108427
- Deokhwan Kim
On Wednesday, August 22, 2012 11:11:06 AM UTC-4, Stefan Monnier wrote:
> I believe this is fixed in the Emacs trunk (where defun is just a macro
>
> that expands to a defalias+lambda and where the docstrings handling was
>
> improved accordingly).
prev parent reply other threads:[~2012-08-23 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 6:07 Surrounding Lexical Variable Reference in the Body of defun Deokhwan Kim
2012-08-22 6:42 ` Andreas Röhler
2012-08-22 15:11 ` Stefan Monnier
2012-08-23 2:56 ` justinhj
2012-08-23 12:52 ` Deokhwan Kim [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=980a4157-dd9f-46c7-8564-3eeb8b8fbc3c@googlegroups.com \
--to=deokhwankim@gmail.com \
--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).