From: Robert Pluim <rpluim@gmail.com>
To: steve-humphreys@gmx.com
Cc: "Philip K." <philipk@posteo.net>,
Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: ielm not described in: An Introduction to Programming in Emacs Lisp
Date: Fri, 18 Dec 2020 11:52:18 +0100 [thread overview]
Message-ID: <87r1nnbd3x.fsf@gmail.com> (raw)
In-Reply-To: <trinity-b2fbd16e-0d62-48bd-812f-a08e4351bd8f-1608287426494@3c-app-mailcom-bs11> (steve-humphreys@gmx.com's message of "Fri, 18 Dec 2020 11:30:26 +0100")
steve-humphreys@gmx.com writes:
>> Sent: Friday, December 18, 2020 at 11:18 AM
>> From: "Philip K." <philipk@posteo.net>
>> To: steve-humphreys@gmx.com
>> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
>> Subject: Re: ielm not described in: An Introduction to Programming in Emacs Lisp
>>
>> steve-humphreys@gmx.com writes:
>>
>> > ielm not described in: An Introduction to Programming in Emacs Lisp.
>> >
>> > Yet there are many reasons for beginners to use ielm. Have some
>> > examples and beginners will get more productive using it as they
>> > delve into new things.
>>
>> I guess it's not mentioned, because it is not necessary, and at least to
>> my knowledge, most people will be using C-x C-e (eval-last-sexp) and
>> C-M-x (eval-defun) in the *scratch* buffer. Using a REPL, when you can
>> evaluate any part of a buffer seems like a step back to me.
>
> I think ielm has more features than just plain evaluation.
>
The one I use most is `ielm-change-working-buffer', which is massively
convenient, and not documented anywhere I can see.
Robert
next prev parent reply other threads:[~2020-12-18 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 2:13 ielm not described in: An Introduction to Programming in Emacs Lisp steve-humphreys
2020-12-18 10:18 ` Philip K.
2020-12-18 10:30 ` steve-humphreys
2020-12-18 10:52 ` Robert Pluim [this message]
2020-12-18 11:03 ` steve-humphreys
2020-12-18 10:39 ` steve-humphreys
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=87r1nnbd3x.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=philipk@posteo.net \
--cc=steve-humphreys@gmx.com \
/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).