newLISP Fan Club

Hah! This is pretty cool 

Some improvement suggestions: support for arrow keys and make `q` and ^C keys work to quit.

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.

😎👍

I normally use Parinfer

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.

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).

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.

Yeah we need someone to act as an active maintainer who can continue the newLISP spirit / way of doing things.

Check out the newLISP manual, and look at the commands under the section Processes and the Cilk API.

Relevant functions: !, exec, process

Edit: also - welcome to the forums!

I heard back from him, he seems to be feeling unwell and is not able to work on newLISP.

I noticed that there's an empty newlisp organization on Github: https://github.com/newlisp

Anyone know whose this is?

It seems like a good idea to get the source up and running on Github, and maybe now is a good time for someone in the community to step up as a maintainer and do that.

That's great news! 

Quote from: rickyboy on June 24, 2016, 10:55:52 AMAgain, you should be banned from this forum.

They've been banned, along with most/all of the other spammers.

Cool set of utilities! Also yeah as you seem to have discovered @ralph.ronnquist this forum has an @mentions feature

Quote from: itistoday on May 22, 2023, 05:25:31 PM(EDIT: I will be surprised if it does, because it's a completely different IP from the IP that Gmail sees for the mail server.)

Indeed it doesn't seem to have helped. But I guess it was worth a try. 

Ah I see what you're saying!

OK, so yes, as I mentioned the rDNS for the mail server is correctly setup to point to the mail server's domain.

However the rDNS for the machine hosting this website doesn't currently point to anything as you pointed out. So yes that's something I can fix - just did that. I don't know how long it takes to propagate, but hopefully should be showing newlispfanclub.com soon. We'll see if that helps with @gmail.com. (EDIT: I will be surprised if it does, because it's a completely different IP from the IP that Gmail sees for the mail server.)

Still, it's very common for one machine to host dozens of domains, and per-machine the rDNS can only point to one of those domains. So this isn't something Google should be checking for when handling email.

Proper spam prevention should not rely on such things IMO, but rather they should use machine learning / deep learning to classify messages. I'm honestly surprised and disappointed that we don't have a good open source solution to this yet.