From: Hongyi Zhao <hongyi.zhao@gmail.com>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: common lisp vs elisp.
Date: Sun, 20 Jun 2021 14:57:49 +0800 [thread overview]
Message-ID: <CAGP6POLcodTVes65p_k2AQcqSv6NMYUoeDFqzocOba745O4N3w@mail.gmail.com> (raw)
In-Reply-To: <87tult2fvq.fsf@fastmail.fm>
On Sun, Jun 20, 2021 at 2:46 PM Joost Kremers <joostkremers@fastmail.fm> wrote:
>
>
> On Sun, Jun 20 2021, Hongyi Zhao wrote:
> > Basically, this means that I can replace ielm with slime
> > (https://github.com/slime/slime) for more comprehensive and advanced
> > functionality.
>
> Well, that very much depends on what you want to do with it. First, Elisp and
> Common Lisp look a lot alike, but they are not identical, nor is Elisp a proper
> subset of Common Lisp.
>
> Second, IELM interacts with your Emacs session. If you set a variable or define
> a function in it, the variable or function is available throughout Emacs. SLIME
> interacts with a Common Lisp subprocess and whatever you do there has no effect
> on Emacs. So you can't define a function in SLIME and then call it from
> somewhere else in Emacs, nor can that function access Emacs' state.
Such being the case, IELM is the only available REPL env for Elisp,
but I'm not sure if it's full-featured.
HY
--
Assoc. Prof. Hongyi Zhao <hongyi.zhao@gmail.com>
Theory and Simulation of Materials
Hebei Vocational University of Technology and Engineering
NO. 552 North Gangtie Road, Xingtai, China
next prev parent reply other threads:[~2021-06-20 6:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-20 2:22 common lisp vs elisp Hongyi Zhao
2021-06-20 3:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 3:26 ` Hongyi Zhao
2021-06-20 3:42 ` 2QdxY4RzWzUUiLuE
2021-06-20 4:04 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-20 4:44 ` Hongyi Zhao
2021-06-20 6:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 6:36 ` Joost Kremers
2021-06-20 6:57 ` Hongyi Zhao [this message]
2021-06-20 7:35 ` Jean Louis
2021-06-20 12:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 15:08 ` Andreas Eder
2021-06-27 15:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-28 6:46 ` Jean Louis
2021-07-06 1:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 12:28 ` Alexandre Garreau
2021-07-06 16:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20 7:16 ` Jean Louis
2021-06-20 7:04 ` Jean Louis
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=CAGP6POLcodTVes65p_k2AQcqSv6NMYUoeDFqzocOba745O4N3w@mail.gmail.com \
--to=hongyi.zhao@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=joostkremers@fastmail.fm \
/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).