From: fig <type9freak@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: [9fans] plan 9 and lisp
Date: Wed, 18 Jan 2023 23:09:24 -0800 [thread overview]
Message-ID: <CANF_3RgD-Mk0Xahs8jDCRYoE=ShOj4dGEOX8Y9vK7XCRS-DfDA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
i’m wondering what 9fans think about lisp, specifically scheme. they’re
both the powerful synthesis of simple ideas. i don’t see any mention of it
as it compares to 9, but they don’t seem incompatible. personally i think
they compliment each other in nice ways.
i don’t have any interest in emacs, i don’t even know what it is. nor
clojure or any of that. i’m talking about lisp being able to manipulate the
structure of the program with tools that are built into the language.
learned about it today.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T7b0afbefb53189b6-Meaf9220ebe5882a4d7497280
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1254 bytes --]
next reply other threads:[~2023-01-19 7:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 7:09 fig [this message]
2023-01-19 11:22 ` Lassi Kortela
2023-01-19 15:28 ` ori
2023-01-19 18:26 ` Csepp
2023-01-19 18:33 ` Jacob Moody
2023-01-19 15:57 ` mkf9
2023-01-19 15:47 ` Bakul Shah
2023-01-19 16:01 ` Dan Cross
2023-01-19 16:13 ` Bakul Shah
2023-01-19 17:07 ` Skip Tavakkolian
2023-01-20 19:45 ` Bakul Shah
2023-01-23 11:31 ` Nick LaForge
2023-01-23 11:45 ` Lassi Kortela
2023-01-25 14:12 ` Ahmed Khaled
2023-01-26 19:34 ` Skip Tavakkolian
2023-01-25 22:59 ` Bakul Shah
2023-01-26 7:18 ` Lassi Kortela
2023-01-26 18:18 ` Tony Mendoza
2023-01-19 11:29 ` Edward Partenie
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='CANF_3RgD-Mk0Xahs8jDCRYoE=ShOj4dGEOX8Y9vK7XCRS-DfDA@mail.gmail.com' \
--to=type9freak@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).