App crashes on start up with `shell.program` set but works from terminal about alacritty HOT 6 CLOSED

@mhfs I'm guessing this is because the PATH doesn't have your Homebrew bins in it when launched from the launcher.

Quickest fix:

[shell]
program = "/bin/zsh"
args = ["-l", "-c", "/opt/homebrew/bin/tmux"]

from alacritty.

hey @nixpulvis, that was spot on. thank you so much for dedicating some time to a new user! ❤️

Even though it's not directly related to Alacritty, I'll leave the details below in case anyone else faces the same issue trying to configure it.

I had Homebrew being bootstrapped from .zshrc which is not sourced during login shells (the -l in the zsh args). I moved it to .zprofile which is loaded by both login and interactive shells and it worked as expected.

From the ZSH documentation:

Commands are then read from $ZDOTDIR/.zshenv. If the shell is a login shell, commands are read from /etc/zprofile and then $ZDOTDIR/.zprofile. Then, if the shell is interactive, commands are read from /etc/zshrc and then $ZDOTDIR/.zshrc. Finally, if the shell is a login shell, /etc/zlogin and $ZDOTDIR/.zlogin are read.

from alacritty.

Strange that launching via alacritty from another terminal works, but the new window action fails.

from alacritty.

Strange that launching via alacritty from another terminal works, but the new window action fails.

Those use different environments. So I recommend checking that.

from alacritty.

@chrisduerr do you mind expanding a little on what those different environments are and how to check the differences? not very familiar with this concept of mixing native apps and terminal settings.

from alacritty.

I'm talking about env. Your system configuration is at fault here, not Alacritty. Up to you to fix that.

from alacritty.