From: Jean Louis <bugs@gnu.support>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: common lisp vs elisp.
Date: Sun, 20 Jun 2021 10:35:38 +0300 [thread overview]
Message-ID: <YM7vyiPXqyrn3dd9@protected.localdomain> (raw)
In-Reply-To: <CAGP6POLcodTVes65p_k2AQcqSv6NMYUoeDFqzocOba745O4N3w@mail.gmail.com>
* Hongyi Zhao <hongyi.zhao@gmail.com> [2021-06-20 09:59]:
> Such being the case, IELM is the only available REPL env for Elisp,
> but I'm not sure if it's full-featured.
I find it more useful than Common Lisp REPL.
If you start observing features, it will allow switching working buffers and
thus context of evaluation. That is like multiple REPLs in same
session. Then you have nice menues and plethora of options not
available in other LISP implementations' REPL-es.
Most of time I use M-: to evaluate quickly, thus all of the Emacs is
one big REPL.
Common Lisp is a pleasure to program. But I have changed almost all
programs from Common Lisp to Emacs Lisp without regret as I got the
user interfaces both in console and GUI. For now I use Common Lisp on
remote servers handling dynamic communication with clients and sending
me encrypted emails. I have a plan to switch that as well to Emacs
Lisp.
My areas of programming are exclusively communications such as emails,
SMS, phone calls, faxes, letters, mostly related to marketing and
relationships with people and the Dynamic Knowledge Repository.
About Dynamic Knowledge Repositories (DKR)
https://www.dougengelbart.org/content/view/190/163/
In other subjects, maybe some heavy calculations, collection of data
from networks, heavy data processing, networking, I could use Common
Lisp.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2021-06-20 7:35 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
2021-06-20 7:35 ` Jean Louis [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YM7vyiPXqyrn3dd9@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.