GNU Aspell VS Steel Bank Common Lisp

So, yeah, no .deb file, no curl/wget, no apt repository that they maintain. OK, cool 😎 no problem. I'll keep looking on Ubuntu side to see if Ubuntu has something 😁 you know. I could see that GNU Aspel's appendix does seem to have a recipe for how to make it myself if I wanted to go that route, as I pointed out earlier, however, since I have Ubuntu, I kept stomping the pavement and then it happened, I was able to... - Source: dev.to / 4 months ago

You might have better luck with aspell. Source: 12 months ago

Sometimes you'll probably have to use some words that are not contained in the default Aspell dictionary used by PySpelling. This is very usual when talking about terms used in technical docs. Look again the configuration example above, and you'll see that we have added a wordlists property to the dictionary one. It makes reference to a .wordlist.txt file, so you can create that file and add your own words to it,... - Source: dev.to / about 2 years ago

For first version I'm just using http://aspell.net english dictionary, but I can easily switch to a custom word list. Will research best options. - Source: Hacker News / about 2 years ago

Tangential: if we're talking Lisp and native code speed, Steel Bank Common Lisp (by default) compiles everything to machine code. [0] https://sbcl.org. - Source: Hacker News / 8 months ago

Q5: Get http://sbcl.org/. Install https://quicklisp.org/. SBCL is the implementation that's the lowest friction, and Quicklisp is a package manager that's almost* painless. Source: 12 months ago

That is what we do in Lisp. Try sbcl if you haven't tried it yet. Source: about 1 year ago

I want to add the sbcl-doc subpackage (the manual for SBCL in GNU Info format), but first I need to understand how to write package definitions. As far as I understand there are the "templates" which are shell scripts that describe how a package is to be built and installed, and xbps-src is a shell script which can process these templates to actually carry out the work. Source: over 2 years ago

> Lisp looks like Python, that's far from C, and usually it's a "interpreted" language, far from machine the currently most popular Common Lisp implementation is based around an optimizing native code compiler. That compiler has its roots in the early 80s. See https://sbcl.org . It's far away from being 'interpreted'. - Source: Hacker News / almost 3 years ago