From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Too fine design granularity leads to numerous macro/function/command existed in Emacs.
Date: Sat, 14 Aug 2021 10:47:05 +0300 [thread overview]
Message-ID: <83bl60bh8m.fsf@gnu.org> (raw)
In-Reply-To: <CAGP6PO+TS5YZHAgSZjC_4_S=p4spu7CVvxnvLWw_OOj6uPASyw@mail.gmail.com> (message from Hongyi Zhao on Sat, 14 Aug 2021 15:25:36 +0800)
> From: Hongyi Zhao <hongyi.zhao@gmail.com>
> Date: Sat, 14 Aug 2021 15:25:36 +0800
> Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
>
> On Sat, Aug 14, 2021 at 3:19 PM Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > > From: Hongyi Zhao <hongyi.zhao@gmail.com>
> > > Date: Sat, 14 Aug 2021 14:29:38 +0800
> > > Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
> > >
> > > > The low-level infrastructure of the Lisp machine
> > >
> > > IMO, by saying ``Lisp machine'', it always means the operating system
> > > is written in lisp, but this is obviously not the case of Emacs.
> >
> > No, I meant the Lisp machine that is part of Emacs core. IOW, the
> > Emacs Lisp interpreter and bytecode-running code.
>
> Can these components be called a ``Lisp machine''? I mean, if without
> the OS it runs on, it can also be called a ``machine''?
Well, that's what I call them.
next prev parent reply other threads:[~2021-08-14 7:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 7:12 Too fine design granularity leads to numerous macro/function/command existed in Emacs Hongyi Zhao
2021-08-13 7:25 ` Eli Zaretskii
2021-08-14 0:46 ` Hongyi Zhao
2021-08-14 6:18 ` Eli Zaretskii
2021-08-14 6:29 ` Hongyi Zhao
2021-08-14 7:18 ` Eli Zaretskii
2021-08-14 7:25 ` Hongyi Zhao
2021-08-14 7:47 ` Eli Zaretskii [this message]
2021-08-13 7:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 8:34 ` Hongyi Zhao
2021-08-13 8:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 9:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 9:26 ` Arthur Miller
2021-08-13 10:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 13:00 ` [OFF TOPIC] Algorithms (was: Re: Too fine design granularity leads to numerous macro/function/command existed in Emacs.) 2QdxY4RzWzUUiLuE
2021-08-13 13:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 13:17 ` Yuri Khan
2021-08-13 13:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 13:48 ` Too fine design granularity leads to numerous macro/function/command existed in Emacs Arthur Miller
2021-08-13 18:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 20:47 ` Arthur Miller
2021-08-13 23:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 0:24 ` Hongyi Zhao
2021-08-14 0:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 1:02 ` Hongyi Zhao
2021-08-14 2:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-14 1:46 ` Arthur Miller
2021-08-13 23:49 ` Hongyi Zhao
2021-08-13 23:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 14:15 ` Eli Zaretskii
2021-08-13 14:42 ` Arthur Miller
2021-08-13 15:59 ` Eli Zaretskii
2021-08-13 17:09 ` Arthur Miller
2021-08-13 18:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 23:40 ` Hongyi Zhao
2021-08-13 23:45 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 23:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-08-13 23:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=83bl60bh8m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.
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).