Christian Duerr

Alacritty does indeed not pass quotes to the shell program executed, if they are 'top level' quotes. This is simply because the command parser interprets them as arguments to Alacritty...

> So I would expect the former to result in an echo process being invoked with an argv of length 4, and in the latter with an argv of length...

That does of course work because there's only one shell involved. An example of what doesn't would be this: ``` alacritty -e zsh -c zsh -c 'cd ~ && pwd...

> Could this be a bug in the Windows build? I don't think it's the multiple shells, because WSL also forwards its arguments. I've attached a couple screenshots with what...

@chrisbouchard Note that you wouldn't want to take a String as input. We already have the args split, just like on Linux. The thing you'd need to do is surround...

> I believe the function I linked last night does what you describe. It does not. You're trying to solve the problem of splitting a Windows commandline into arguments. We'd...

> I'm getting quite frustrated with this. I am not re-splitting the argument list. This function is looping over a single argument. Fair enough. I thought you were suggesting to...

Can you provide a screenshot?

Please share the actual configuration and font name you've picked. Only because it works in Windows Terminal does not mean you've specified things correctly.

Are you positive the configuration file you're editing is actually being loaded?