Found a nice talk on concurrency. It has a very brief comparison of different concurrency models, like Erlang's Actors, Hoare's CSP, Go's goroutines, Clojure's core.async, Concurrent ML (aka Fibers in Guile).
Primary focus on Concurrent ML (but examples are in Scheme with type annotations ><).
Part1: In Emacs there is a super useful command: C-u C-space set-mark-command
that allow to return to recent place where you was doing anything. 🤘
But I have problem with this command in Org-mode - it doesn't expand headers
tree and text around it header was fold. 💔
The reason for this was in "Sparse Tree" feature and historical approach:
entire document is folded as much as possible.
That is why, as I understand, (org-fold-show-entry) and (outline-show-entry)
hide some headers and text.⛇
To show this text there is command for it:
C-c C-r (org-reveal)
I don't know why this command require '(4) parameter to work properly. ¯_(ツ)_/¯
I wrote hook that will automatically call org-reveal with appropriate
parameter '(4):
(add-hook 'org-mode-hook (lambda ()
(advice-add 'org-fold-show-context :after (lambda (&rest args) (org-reveal '(4)) ))
))
⛅ #emacs#elisp#lisp#org-mode #orgmode
⚰
I think the naysayers of scheme could benefit from reflecting on the Talmud's advice to choose "the longer shorter way"
Rabbi Yehoshua ben Chananiah:
Once a child got the better of me.
I was traveling, and I met with a child at a crossroads. I asked him, 'which way to the city?' and he answered: 'This way is short and long, and this way is long and short.'
I took the 'short and long' way. I soon reached the city but found my approach obstructed by gardens and orchards. So I retraced my steps and said to the child: 'My son, did you not tell me that this is the short way?' Answered the child: 'Did I not tell you that it is also long?'
(Talmud, Eruvin 53b)
#Scheme on the other hand renders your long-term goals exceedingly near by forcing you to take the long way, which is ultimately the shorter way, because once you forgo piles of features in order to focus only on the tools that are essential for implementing the features you need, only then will you be free to discover the right way.
I'm looking for a Lisp resource I run across but can't find anymore.
It's a Common Lisp reference similar to the HyperSpec or possibly based on its text, but with a clean web design and modern HTML formatting. The name of the resource rhymes with "spec" or "hyperspec".
In the Lisp community @lisp on Lemmy.ml there's a discussion on what your Lisp development environment looks like and how you got started with Lisp. Of course I'm the weirdo who uses Interlisp as his daily driver.
Don't how I missed the news about this project to write a Desktop Environment in Common Lisp! And it looks like it already has some cool demos! #lisphttps://codeberg.org/mmontone/mold-desktop
While I'm not personally particularly interested in old computers (beyond PDPs & LMs), I'm extremely interested in people designing their own 8/16bit computers, and the exploration of #8bit / #16bit computing as a living medium, rather than as relics of primarily nostalgic value.