From: Katsumi Yamaoka <yamaoka@jpl.org>
To: schwab@linux-m68k.org
Cc: emacs-w3m@namazu.org, emacs-devel@gnu.org
Subject: Re: labels usage
Date: Tue, 12 Jun 2012 16:48:22 +0900 [thread overview]
Message-ID: <b4mehplc6nt.fsf@jpl.org> (raw)
In-Reply-To: m2mx49f0ul.fsf@igel.home
In [emacs-w3m : No.11847] Andreas Schwab wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> Is this a wrong usage?
>>
>> (let (fn)
>> (labels ((fx (arg) arg))
>> (setq fn 'fx))
>> (funcall fn 99))
> You should use #'fx instead.
Ok, we *should* use #' from now on. This was what Michael Heerdegen
wrote in the emacs-w3m list a while ago. Maybe it didn't go well
when I tried it was I forgot to build emacs-w3m from scratch. I'll
try it again. Thanks.
next prev parent reply other threads:[~2012-06-12 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 6:53 labels usage Katsumi Yamaoka
2012-06-12 7:25 ` Andreas Schwab
2012-06-12 7:48 ` Katsumi Yamaoka [this message]
2012-06-12 13:07 ` Stefan Monnier
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=b4mehplc6nt.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-w3m@namazu.org \
--cc=schwab@linux-m68k.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).