alacritty: can't find config file on windows!

You should put it there yourself. We’re not creating a config and other random permanent files for you, it’s expected.

Another note, the Windows installer doesn’t create the default C:\Users\<your_user_name>\AppData\Roaming\alacritty\alacritty.yml config file. The installer could easily create this directory and copy the default all commented-out config into it, but it doesn’t… which is quite user friendly, you need to figure this out yourself because the README doesn’t say anything about the provided default config template.

everything is mentioned there https://github.com/alacritty/alacritty#configuration

IIRC you can run alacritty in ConEmu, so in theory if cmder is a ConEmu fork, you can run alacritty in it, but I’m not an expert here.

The location should be C:\Users\YOUR_USERNAME\AppData\Roaming\alacritty\alacritty.yml IIRC.

ConEmu setup was touched there https://github.com/alacritty/alacritty/issues/3173

This should be in the README, currently there’s a wrong path for Windows user. No deal-breaker but this wastes your users’ time.

The path in readme isn’t wrong, it’s correct, since it’s using environment variable, and should auto expand. The path in readme is exactly the same we’re using internally, when we’re searching for config.

While technically it is correct, it can be misleading (I was mislead by it initially too). It would be helpful to new users to mention it to parenthesis something like this: (%APPDATA% usually expands to C:\Users\<your_user_name>\AppData\Roaming)

More often than not, there is a big difference between “technically correct” (but terse), and useful/helpful documentation 😉

%APPDATA% is how Windows specifies environment variables. So it’s not necessarily the location @kchibisov pointed out, though that is most likely. You should check the %APPDATA% environment yourself.

likely no, vscode uses its own terminal IIRC. So you can’t integrate anything into it, I guess. But I’m not an expert here. However if you can open any terminal in vscode or let’s say Firefox(random browser), you can likely open alacritty too.

Just to make it clear, we’re not cmd.exe,pwsh.exe, etc. We’re actually a terminal emulator, not a shell, like cmd.exe and friends.

The location should be C:\Users\YOUR_USERNAME\AppData\Roaming\alacritty\alacritty.yml IIRC.

This should be in the README, currently there’s a wrong path for Windows user. No deal-breaker but this wastes your users’ time.

is there a way to integrate it within vscode and not open a separate instance?

yes, you can configure by opening vscode directly or use this:

1. cd %APPDATA%/roaming/alacritty

2. code .

the file will open on vscode

Executable is always installed in the place where you need extra privileges to operate. If you want a different place for a config file, you can pass --config-file args on the command like which you can set on windows a an application settings.