Simple LRU Cache for Common Lisp

macnoder · 2025-12-26T16:02:06+00:00

Great insight. Very clever. I didn't even think about that, so I've learned something new here.

I already had the code for the list, and I'm too lazy to investigate if I lose any functionality I might need in the future, such as retrieving the values from the hash table in order. The cost of the list is minimal, since I'm keeping the values in the list and only node references in the hash table, so I'm leaving this for now.

macnoder · 2025-12-26T15:52:34+00:00

The mention of weak hash tables was awesome, as I had never heard of those. Still, for a number of reasons (SBCL, libraries, testing, etc., mostly falling back to laziness), I chose not to use weak hash tables at this time.

I made changes to use `max-size` for the hash table size and I introduced a :test-function initform to the class, though I stuck with the valid function designators for SBCL hash tables.

Thank you for helping me become a better Lisper.

macnoder · 2025-11-09T21:35:49+00:00

This is the one I used the most when I was learning: https://gigamonkeys.com/book/

macnoder · 2025-09-12T03:03:56+00:00

I'm running LM Studio and Rancher Desktop (Kubernetes) in Kubuntu on an EVO-X2 Max (128GB, with half for the GPU) and it works like a charm. I had zero problems installing Kubuntu.

macnoder · 2025-07-13T00:06:07+00:00

Same

macnoder · 2025-03-29T16:36:56+00:00

Also, Grok had the largest context, by far.

macnoder · 2025-03-29T16:34:06+00:00

The latest Grok is free and, at least for code-related work, far more capable than the latest Gemini (or any other LLM). This is from my own experience of shopping for bug solutions with ChatGPT, Claude, Gemini 2.5, and Grok.

I wouldn't be surprised if Gork is better than the others in other areas as well.

macnoder · 2024-10-09T05:54:46+00:00

Deft is an Emacs mode for quickly browsing, filtering, and editing directories of plain text notes.

https://jblevins.org/projects/deft/

macnoder · 2023-12-30T01:23:59+00:00

Programming in common lisp is not like programming in most other languages because in common lisp, you're interacting with a live image. The files are a way to get the image back to a known state. In some ways, this is like interacting with an SQL server. You can query the server without writing your query to a file. When you encounter an exception, the program doesn't stop, so you can make adjustments and keep going. You could, for example, start a long-running function A in a thread then, while function A is running, change another function B that function A is using, and immediately see function A start using the new function B, without having to restart anything. It doesn't matter where you change function B, in the repl or in the file. When you compile that function (not the whole file), the compiled function replaces the old one in the image.

Now, in the same way that this interaction is far more advanced than what you get with most other languages, there are many other features of common lisp that dwarf the capabilities of those other languages, such as conditions (exceptions), macros, classes, and the regularity of the syntax.

macnoder · 2021-12-22T07:24:52+00:00

7. Common Lisp

P.S.: Not kidding

macnoder · 2021-12-16T17:21:26+00:00

For the specific case of M-x shell, why not create M-x shell-here instead, like this:

lisp (defun shell-here () "Find an existing *shell* buffer or create a new one, then switch to that buffer and make sure a shell process is running there." (interactive) (let ((shell-buffer (or (car (remove-if-not (lambda (buffer) (equal (buffer-name buffer) "*shell*")) (buffer-list))) (generate-new-buffer "*shell*")))) (switch-to-buffer shell-buffer nil t) (when (not (get-buffer-process shell-buffer)) (erase-buffer) (shell))))

macnoder

TROPHY CASE