CuteVim VS buildroot

BTW you should package your emacs config file with the emacs APE to do a cuteemacs, to carry your config files and everything in a portable binary: https://github.com/csdvrx/CuteVim

Another idea: have you considered that the "program that would be run by .bashrc" to generate the "unambiguous 24-bit color capabilities" could set environment variables to communicate them? Like, if you can't stuff them in terminfo, stuff them in environment variables! Env var work well on Windows, and the configuration files of terminal programs could just use these when available to override.

It's be like adding friends to your proposed TERMVERSION: TERMSETF24 etc

for vim aarch64 and x86-64 : https://github.com/csdvrx/CuteVim

just embed your own vimrc with zip following the instructions

for others, see https://cosmo.zip/pub/cosmos/bin/

> That being said, the config is definitely highly personal

I have very special preferences (like CHORDING EVERYWHERE! :) )

> it would be amazing to have a set of scripts to compile one's own personal .vimrc

Actually, I thought about people who may have different preferences!

If you want to do the same thing but with your own .vimrc, just check the "How can I make my own CuteVim APE?" section in the README (https://github.com/csdvrx/CuteVim?tab=readme-ov-file#how-can...)

This section documents the use of the refresh.sh script from https://github.com/csdvrx/CuteVim/blob/main/refresh.sh

> and related config files (really, the entire .vim directory) into a single APE.

I don't like having a billion files everywhere (like plugins/ etc) so I didn't think about that usecase, but that would be a great addition because most people have a .vim tree: even with my dislike for having too many files, I have myself a few in .vim/after/syntax/ (to apply italics to comments)

If you can contribute a script that converts your .vimrc and .vim/ tree into something that can be added to the APE, I'd be very happy to add it!

Tesla uses Qt and Qt WebEngine uses Chromium, meaning that there is probably in fact a V8 JavaScript engine in any given Tesla.

https://github.com/teslamotors/buildroot/tree/buildroot-2021...

It uses buildroot: - https://github.com/teslamotors/buildroot - https://lists.buildroot.org/pipermail/buildroot/2018-May/221323.html

> Its actually the other way around. Tesla cars are designed more like SpaceX rockets or fighter jets in terms of electronics.

Yeah, the SpaceX and Tesla software stacks for their firmware are similar in a lot of ways, they both heavily use buildroot(https://buildroot.org/) for at least a good bit of their Linux based firmware, good luck getting proper GPL source from them though, Tesla last I checked at least made some effort to publish what appears to be incomplete buildroot source code(https://github.com/teslamotors/buildroot).

SpaceX just inaccurately claims "Because we are not distributing buildroot, we are not legally required to distribute the source code under the GPLv2 license." then ignores you even though they very obviously distribute buildroot based firmware to customers as it's used in the Starlink Dishy antenna(I asked for their buildroot source and have a Dishy antenna, that was their response...and to top it off I'm even a major buildroot contributor). They def have a bunch of cool tech but are super secretive about everything it seems, they don't appear to ever upstream patches or interact with outside software developers.

Uh. There are a lot of things you're getting very wrong here. First, Tesla's OS is absolutely Linux. It may not be running the GNU software stack, but that makes it not a GNU/Linux. Though, I'll point out that it's running the Busybox software stack as well as custom software. Please feel free to review the buildroot build system for Tesla's car OS. https://github.com/teslamotors/buildroot