-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Lisp introduction for the book, part 1 #195
Conversation
Thanks for the PR - I will take a look in the next few days |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to make the distinction between Scheme and Lisp? I don't mind referring to steel as a member of the lisp family (since it is) but in general its origin bears much closer resemblance to scheme, and I'd like that to be reflected in the documentation
hey, I tried to frame it more as a descendant of Scheme now |
Just the one nit, otherwise I think this looks okay - did you want to get this merged as is? Or continue adding things? |
Thanks for the review, I planned to do more PRs to make them more manageable as I'm not quite sure where is the point when I find it "done", so this one could be merged |
Hello @mattwparas,
First of all, I'd like to thank you for your efforts in making embedded Lisp for Rust, as well as advocating for it through the actual implementation of a plugin system for Helix.
I've been observing responses from individuals who are resistant to the idea of Lisp as an embedded language for the editor, and in response I've taken it upon myself to write an introductory Lisp chapter for the book. My hope is that this will help broaden the reach of the project and make it more approachable.
While my work is not yet finished, I wanted to share my progress early. If this idea resonates with you, I am eager to continue my efforts.