From: Andrew Taylor <ataylor@its.to>
Subject: Re: evaluate expression in scratch buffer
Date: Thu, 22 Apr 2004 22:23:52 GMT [thread overview]
Message-ID: <YBXhc.220744$oR5.170503@pd7tw3no> (raw)
In-Reply-To: <c69c00$7et$1@news.island.liu.se>
William Payne wrote:
> Hello, I want to evaluate the following expression:
> (insert (prin1-to-string (w32-select-font)))
>
> I read that I should evaluate it in the scratch buffer, so I typed it in
> there...but what do I do to get the actual evaluation to occur?
In lisp-interaction-mode (which is what the *scratch* buffer uses), C-j
is mapped to eval-print-last-sexp. Just position the point after the
last closing parenthesis and press C-j.
--
Andrew
next prev parent reply other threads:[~2004-04-22 22:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 21:04 evaluate expression in scratch buffer William Payne
2004-04-22 21:27 ` Marco Parrone
2004-04-22 22:23 ` Andrew Taylor [this message]
2004-04-23 6:20 ` Holger Sparr
2004-04-23 16:11 ` Kevin Rodgers
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='YBXhc.220744$oR5.170503@pd7tw3no' \
--to=ataylor@its.to \
/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).