From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Lookarounds and recursion in Emacs regexes
Date: Mon, 06 Feb 2023 14:44:30 +0100 [thread overview]
Message-ID: <87357i7vsx.fsf@dataswamp.org> (raw)
In-Reply-To: 838rhbq66a.fsf@gnu.org
Eli Zaretskii wrote:
>>>> It doesn't prevent adding other extension languages, nor
>>>> even does it necessarily prevent changing the
>>>> implementation language to another one in theory.
>>>
>>> Indeed, but replacing ELisp would probably need to rewrite
>>> a lot of internals currently implemented in C, since most,
>>> if not all, of them are currently very tightly coupled
>>> with Lisp and assume the existence and
>>> design/implementation of various aspects of the
>>> Lisp machine.
>>
>> I don't think anyone suggests replacing Elisp
>
> Stefan did, in the part cited above. he didn't suggest it,
> but he said it's not prevented. And I replied to that part.
It depends, I suppose as long as that's only part of
the reply?
--
underground experts united
https://dataswamp.org/~incal
prev parent reply other threads:[~2023-02-06 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 14:11 Lookarounds and recursion in Emacs regexes Evan Aad
2023-01-27 18:12 ` Marcin Borkowski
2023-01-27 19:30 ` Emanuel Berg
2023-01-28 6:46 ` tomas
2023-02-03 19:22 ` Emanuel Berg
2023-02-04 15:46 ` Jean Louis
2023-02-04 21:48 ` Emanuel Berg
2023-02-07 9:46 ` Jean Louis
2023-02-07 10:25 ` Emanuel Berg
2023-02-07 22:45 ` Jean Louis
2023-02-26 11:40 ` the GLIMPs [GIMP Lisps] (was: Re: Lookarounds and recursion in Emacs regexes) Emanuel Berg
2023-02-27 8:31 ` tomas
2023-02-04 22:28 ` Lookarounds and recursion in Emacs regexes Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-04 22:44 ` Emanuel Berg
2023-02-05 5:51 ` Eli Zaretskii
2023-02-06 12:53 ` Emanuel Berg
2023-02-06 13:09 ` Emanuel Berg
2023-02-06 13:23 ` Eli Zaretskii
2023-02-06 13:44 ` Emanuel Berg [this message]
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=87357i7vsx.fsf@dataswamp.org \
--to=incal@dataswamp.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).