The Complete Computing Environment
CCE is the amalgamation of Tools I use to build a computer I don't hate. It's primarily a distribution of Emacs and Fedora Linux embodying an ideal of modern modal interface, and a focus on Knowledge Management through org-mode to produce independent knowledge work. It is implemented and justified through the following documentation, Emacs Lisp source code, and Ansible task and role definitions. This system is a Literate Programming project, a collection of configurations and simple software written with the mental inputs which went with its creation, basically. Each page is loaded up by the code in this document, source code is extracted and compiled, and then evaluated, an
init.elc created for the next boot's benefit.
This is not an Open Source Project, nor is it a public wiki. These documents mainly exists to be consumed by me as an org-mode meta application existing within my Concept Operating System. It can eventually be consumed by others through the World Wide Web. It is not designed to be built on top of by others except as a collection of concepts and ideas and implementation details. It is not designed to be "used" by others, per se, outside of copying and pasting code from changes delivered eventually via RSS. "don't @ me"1 about this. Post changes to your blog, publish your own wiki, or host it via GitLab if you seek to build a shareable solution or a community. I am happy to move on to well-supported library solutions as opposed to my own tin-can code, so take my contribution to the commons and expand upon it if you want. I do not want to be a maintainer of an Open Source Project. This is a space for me to explore and to learn about myself and my world. Build your own tools and collaborate with me over high-bandwidth communication protocols. Find me on Matrix if you wanna talk about this –
This code will "tangle" the org-mode files' source code out to individual files:
let ((modules (cce/module-list))) (mapc (lambda (l) (org-babel-tangle-file (car l))) ( modules))
Here are the modules that the indexer can see:
This is Referenced
The substrate for CCE: The Complete Computing Environment, a programmable Lisp Machine which is also a text editor.
And so I've withdrawn, and built The Complete Computing Environment for myself, built the first iteration of Arcology knowing that no one else could use it, all while of course feeding this monster of capital in my own way. But as this vision comes together, I think there is a future where these things can be shared, where a private network can be operated by three or four people and serve the needs of 20 or 50. I think that society could structure itself in this fashion more. Small community and familial collectives, providing for each other in spite of the rest of the world. I know I'm a fool. The point is that I would like to live in a world which respects its inhabitants, and that those inhabitants respect the world. As our world is shut down and isolate, gripped in fear of COVID-19, I see signs that I am not the only person looking for solutions towards the increasingly visibile inequity around me. And so, I have decided once again to sharpen the axe, to find a point on the map of space-time-culture and walk towards it with purpose.
I describe The Complete Computing Environment half-seriously as a Concept Operating System.
Navigating the Arcology is supposed to be a somewhat curated experience. I either send out a direct link to a page, and people can read and explore from there, or they go to one of the index pages like The Arcology Garden, The Complete Computing Environment, or The Lion's Rear. Those index pages are carefully curated, if not to send people on a romp through the respective garden, then to at least not get lost if they go back to that page.
This code runs at the end of the
initfile generated in my Index of CCE Functionality. Throughout the CCE, there's code which attaches functions to
after-cce-hook((deadgrep "after-cce-hook") to take a look), this makes sure they're run after everything else is initialized.
The Complete Computing Environment is at its core a set of documentation, a pile of org-mode files and code that extracts the source code from those files before compiling and ultimately running that code. In the original implementation of CCE, there was a hard-coded list of files to load code from, and managing this over the years has become complicated. Eventually I expanded the CCE to also manage my server, opting to push all of that in to a single file.
This is the package manager configuration for CCE: The Complete Computing Environment
in "Mood Log"
Build Practice Captures for recording my mood and graphing over long term CCE. It's funny, I never actually did this, and maybe this says more about how I am using this software: I have been using this as a Topic Files within the Journal. So, this informed the design of the defdaily system, a system evolving.
In The Complete Computing Environment there are a number of processes that I run that I want to have more visibility in to than if they were running as SystemD User Services. They may die, they may start to spawn errors, I want to know if it's failing or misbehaving. Right now this is mainly used in my OfflineIMAP setup, but I maintain it here and use it for one-off solutions.
Candidate for CCE module to restore unread message counts in Gnus, even with
MaxMessagesset in mbsync configuration. with
MaxMessages 1000, my
~/Maildiris 8.0 gb, probably from A bunch of cool tumblrs which I might move in to an actual Tumblr account again.