unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Lookarounds and recursion in Emacs regexes
Date: Sat, 04 Feb 2023 23:44:57 +0100	[thread overview]
Message-ID: <87h6w1jbiu.fsf@dataswamp.org> (raw)
In-Reply-To: jwvv8kh83xi.fsf-monnier+emacs@gnu.org

Stefan Monnier via Users list for the GNU Emacs text editor wrote:

>> [re: Elisp, I heard GIMP once used Lisp as its
>>  configuration/extension language, only at some point switched
>>  to Python for that. That's not gonna happen to Emacs, is it?
>>  *runs away*]
>
> There's a common confusion that ELisp is some kind of
> extension language for Emacs. That's not quite true.
> ELisp is an *implementation* language of Emacs (along with
> C for the other half).

Okay, so Emacs is implementation, configuration _and_ extension.

C is to most implementation and that's it and unawarely so
probably most often, but with dynamic modules, it can be
extension as well, I suppose it could be configuration as well
but again in practice who does that and what benefit would
that be ...

Or am I wrong?

> It doesn't prevent adding other extension languages, nor
> even does it necessarily prevent changing the implementation
> language to another one in theory.

I know!

> But in practice it has discouraged most attempts to provide
> another language (except arguably for the "statically scoped
> dialect of ELisp", because its interoperability with the
> original ELisp was sufficiently smooth).

But didn't you have the idea of adding a third layer language,
don't remember what that idea was, the language was to be
created for this purpose so a brand new one was discussed,
maybe it stopped at discussions?

What would have been the idea with that?

People say Emacs Lisp is slow but to me it feels pretty fast?

But I think there are other problems - lack of standard
libraries - a lot of functions everywhere that do similar
things, do-something do-the-same-buffer do-the-same-region
do-the-same-no-properties etc. Too much looking up stuff all
the time is a problem. Also too long words all the time ...
reduce typing to increase development speed. so start -> beg,
`require' -> req, `expt' -> **, all that, also make all final
args of functions where nil makes sense optional so trailing
nils can be pruned, just reduce typing if one cares
about speed.

Its biggest problem? It's too sexy for it's shirt!

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2023-02-04 22: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 [this message]
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

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=87h6w1jbiu.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).