Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - itistoday

#1
newLISP newS / Re: Forked newLISP – Meet Rebel
December 01, 2025, 09:39:46 AM
That project seems relatively unknown and abandoned afaict
#2
newLISP newS / Re: Forked newLISP – Meet Rebel
November 16, 2025, 02:10:47 PM
I'd love to see some improvements to interacting with CLI programs. It's been a long time since I've done this but I remember that newLISP had issues when it came to managing the input / output of running programs, especially when combining piping data in to the program and getting data back out from both stdout and stderr, and handling errors.
#3
newLISP newS / Re: Forked newLISP – Meet Rebel
November 16, 2025, 02:00:54 PM
Quote from: ufko on November 16, 2025, 09:53:32 AMI believe Rebel v1.0 is currently the most stable incarnation of the newLISP codebase.

That's awesome. Following  8)
#4
newLISP newS / Re: Forked newLISP – Meet Rebel
November 15, 2025, 01:15:16 PM
Woah this is awesome! Congrats Ufko! I'm excited to see where this goes, please keep us posted of updates!
#5
newLISP newS / Re: Wisp to new lisp
June 13, 2025, 04:44:12 PM
Yeah same here, parenthesis make everything easy to understand for me, I honestly don't get why anyone hates them.
#6
Nice!
#7
I think experiments that people want to put effort into are worth trying. 👍
#8
newLISP newS / Re: newLISP Github?
February 28, 2025, 08:57:15 PM
When I asked Lutz this question he got back to me with a link to the same repo @iacore posted: https://github.com/kosh04/newlisp

So I guess maybe that's where people should look to send PRs? But I see nobody seems to be maintaining it, and it seems to be setup more as a mirror.
#9
newLISP newS / Re: newlisp.org website down
February 28, 2025, 12:30:29 PM
It's back up!
#10
Hah! This is pretty cool  :D

Some improvement suggestions: support for arrow keys and make `q` and ^C keys work to quit.
#11
Quote from: pber on April 15, 2024, 07:13:47 AMMany thanks, itistoday, for you effort on newLISP.

🙇�♂️

Quote from: pber on April 15, 2024, 07:13:47 AMI`m studing his codebase and I`m starting to feel a profound feeling of respect and regard for him and his code, which is great (IMHO).

I hope to publish something about my project (Ike) in order to find help from you Lisp coders.

😎👍
#12
I normally use Parinfer
#13
Quote from: marchildmann on August 07, 2023, 07:51:56 AMThank you Greg for managing the new forums!
Just re-registered because my previous nickname "hilti" was taken.

Cheers
Marc

Welcome back @marchildmann!

FYI your previous username should still belong to you. Try resetting the password for that username. If you still have control over that email you should get an email letting your reset it.
#14
newLISP newS / Re: newLISP Github?
August 03, 2023, 09:36:23 AM
Quote from: iacore on July 31, 2023, 01:21:52 AMI have fixed some bugs of newLISP here: https://git.envs.net/iacore/newerlisp
I also added `(write-expr x)`. May you find this useful.

Have you considered putting out some release notes? Feel free to take inspiration from how Lutz does it or create your own method (e.g. a simple `HISTORY.md` file is often useful).
#15
I know there's a `newlispdoc` utility that creates documentation based on code comments. I'm not sure if that's used to build the full manual though.