CuteVim VS hydra

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!

You can also use Hydra for Emacs.[1] Once I discovered how to configure Hydra, I made it a habit to make one for every new major mode I need to use.

[1] https://github.com/abo-abo/hydra

Have you considered a hydra?

An Emacs specific example: I'm working on a few go projects at the moment and go requires recompilation after changes. Step one was finding auto-recompilers for my projects (I'm using both air and reflex in various projects). Step two was realizing that I spent a lot of time switching to the buffer where the output is printed, so I wrote a little hydra menu to make that easier. Then I found myself having to restart those processes each time I restarted Emacs, so I went digging and found detached to manage the processes. Then I got tired of having to hunt for where the detached output was displayed in my frame so dug into sidebars to manage the windows more effectively.

I think the goal of the hydra package is to provide such functionality.

I would I also encourage anyone who does not want to use modal editing to look into repeat-mode, hydras, and key-chord.

The C-c prefix is designed for you, the user, to use for your nefarious deeds. Some things that may help with both binding and knowing what key does what would be a menu such as hydras or transient menus (which apparently are part of Emacs now so that's new).

For the very same reason, I started to use hydras: https://github.com/abo-abo/hydra - see my config at https://github.com/novoid/dot-emacs/blob/master/config.org

Hydra lets you define mini-modes with limited scope.

general.el also works well with hydra.el. Here's my hydra for window operations - it activates when I press ,w: