Great write-up, but I also want to point out that alacritty is pre-packaged for many Linux distros. On Fedora, I could just run sudo dnf install alacritty. Definitely useful information here either way, and I agree that their homepage does not make this clear at all, but you can likely skip the whole Docker thing unless you have a specific need to run the build manually.
I'm trying to use Alacritty with some custom startup overrides. Annoyingly, setting the window size does not work. It just silently ignores it. It always opens at the same size (100x35). Note that I have not set these settings in alacritty.yml.
Those are the main parts in my configuration. I'm still discovering new things
and updating my alacritty.yml file from time to time. Be sure to follow my
dotfiles repo to see the latest changes:
In principle, you should know the details of your installation procedure in order to be able to fully undo the installation. In as far as I see, everything from the compilation is under a target/release/alacritty somewhere. From there, you manually moved things out to /usr/local/bin and other places, as indicated under Desktop Entry. Just undo these actions.
I believe the updating alacritty from the source code would be more advisable at any point compared to installing from apt repos. I have suffered crashing at certain instances while using apt after upgrading my system.
Usually i just do apt remove "package" but it says can't find the package, so i don't know what to do, sorry im very new at linux,oh also i've tried to npm remove alacritty-themes but the output is up to date
4. Once the compilation process is complete, the binary will be saved in ./target/release/alacritty directory. Copy the binary to a directory in your PATH and on a desktop, you can add the application to your system menus, as follows.
7. Finally start Alacritty in your system menu and click on it; when run for the first time, a config file will be created under $HOME/.config/alacritty/alacritty.yml, you can configure it from here.
I would like to use neovim for editing the markdown files. joplin is able to open neovim, but it opens on xterm and I would like to use alacritty instead. I have used the option in tools>options>general>path to use alacritty -e nvim which should start alacritty with neovim. but for some reason it does not open the file neither neovim or alacritty. I would like to know if it is possible to even use alacritty here or not.
See here for an example of the how you can change your alacritty.yml configuration file to allow for toggling between different colors schemes. Most of the configuration file has been omitted, only the relevant parts remain where there is the addition of a new key color_schemes that is a mapping to different color schemes you want to have available. Node anchors on each scheme allow referencing these schemes by referencing them in the colors attribute.