From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: the GLIMPs [GIMP Lisps] (was: Re: Lookarounds and recursion in Emacs regexes)
Date: Sun, 26 Feb 2023 12:40:13 +0100 [thread overview]
Message-ID: <87zg90wt7m.fsf_-_@dataswamp.org> (raw)
In-Reply-To: Y9TEwfblvPagZYja@tuxteam.de
tomas wrote:
> Actually a Scheme [0]. And actually, it's still in, besides
> Python, Perl and Tcl [1]. Of course, I do prefer script-fu.
> Although somewhat proficient, I never learnt to love Python.
Everyone says that ... my COMP-HIST automation [1] indicate
that this is about GIMP?
As Python (Gimp-Python) is now the main (only?) extension
language for GIMP - previously SIOD, TinyScheme, and
Script-Fu.
<incal> ,, hist Scheme, Perl, Tcl, SIOD, Python, TinyScheme, Script-Fu
<sth> Scheme 1975 lexical Lisp. MIT, Guy Steele and Gerald Sussman [MacLisp]
<sth> Perl 1987 Unix scripting language, Larry Wall
<sth> Tcl 1988 ("tickle") interpreted, compact programming language
<sth> SIOD 1988 Scheme In One Defun/Day, interpreted extension language
<sth> Python 1991 interpreted OO. significant whitespace. name from UK show
<sth> TinyScheme interpreted extension language, e.g. previously for GIMP
<sth> Script-Fu 1998 GIMP extention language based on TinyScheme
[ Anyone knows when TinyScheme came? doesn't say here, or am
I blind? https://en.wikipedia.org/wiki/TinyScheme ]
> I'm nearly certain it was derived from SIOD; the Wikipedia
> below says it's Tiny Scheme. Dunno which one is right.
Tomás, you are almost always right. Why don't you write
a book/booklet on computer history? If you do, I can edit it
in very neat LaTeX with diagrams and lists and stuff.
Including the last list, what is it called, the index?
But without the pretentious introduction (yuk).
[1] https://dataswamp.org/~incal/#sth
https://dataswamp.org/~incal/sth/scripts/hist
https://dataswamp.org/~incal/COMP-HIST
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-02-26 11:40 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 ` Emanuel Berg [this message]
2023-02-27 8:31 ` the GLIMPs [GIMP Lisps] (was: Re: Lookarounds and recursion in Emacs regexes) 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
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=87zg90wt7m.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).