wl-gammactl VS CuteVim

I don't know what you mean by color management - is it the calibration of the display with xrite/argyll?

For ICC profiles colormgr can help: https://wiki.archlinux.org/title/ICC_profiles#Wayland

If you just need basic brightness, contrast and gamma, wl-gammactl should do that: https://github.com/mischw/wl-gammactl

BTW Hyprland is not required, it's just the most practical way to have shortcuts key mappings in Wayland

However, this does not work in Wayland since it obviously belongs to the X Window System. I started searching the web for a possible solution and found wl-gammactl, which is a GUI for wlroots (https://github.com/mischw/wl-gammactl) and the gnome-gamma-tool (https://github.com/zb3/gnome-gamma-tool), but neither of them seemed to work because of missing dependencies, which can't be installed or invalid version numbers of required packages (e.g. found 1.20 but need: '>=1.23'). When attempting to build the gnome-gamma-tool, the following error message appears (despite Colord being installed):

It's very much possible with Wayland. Whether Plasma supports it is another question, unfortunately. Great program though, you can control it with commands and set an invert screen colors keybind.

What would be the best way to implement this? I tried wl-gammactl https://github.com/mischw/wl-gammactl with those settings but the screen just goes fully white?

Probably it just support sway as said here on github

Wayland is the protocol applications use to talk to compositors. What you need to control (this kind of-, since I assume you want a software overlay) brightness depends on the compositor/desktop environment you use. For wlroots based compositors (wayfire, sway) wl-gammactl or wlr-brightness could be useful. For Gnome (below version 40) the soft-brightness extension looks like what you need.

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!