On occasion I use the dwl window manager. I'm not sure if this is an upstream issue, though I have similar problems using it with Fedora.
At any rate, I have a set of environment variables that I use if inputting Japanese with fcitx5. Problem 1 is, the only way I can get these variables set in dwl is to declare them in .bashrc, .zshrc, or .zshenv. I tried running a script export XMODIFIERS=@im=fcitx but it will only work with the terminal that I use to run the script. I'm guessing it opens a subshell, but anyway, that's not the main issue.
If I use labwc (which has a section in $HOME/.config/labwc to set environment variables), everything works as it should. In dwl, however, I can't input Japanese in alacritty, even if echo $XMODIFERS, etc., are showing correct environment variables. I also can't get it to work in firefox, though it does in chrome. (Also works in libreoffice). I can get it working in a urxvt terminal.
As this seems specific to dwl, I *think* it may be an upstream issue, but, while I realize this is an edge usage case, figured I'd ask in case anyone has run into it and solved it. (FWIW, in Fedora, I can't even open urxvt in dwl, with a message of can't open display :0, though it works in Fedora's labwc, but I figure that's a Linux, or more likely, Fedora issue).
At any rate, I have a set of environment variables that I use if inputting Japanese with fcitx5. Problem 1 is, the only way I can get these variables set in dwl is to declare them in .bashrc, .zshrc, or .zshenv. I tried running a script export XMODIFIERS=@im=fcitx but it will only work with the terminal that I use to run the script. I'm guessing it opens a subshell, but anyway, that's not the main issue.
If I use labwc (which has a section in $HOME/.config/labwc to set environment variables), everything works as it should. In dwl, however, I can't input Japanese in alacritty, even if echo $XMODIFERS, etc., are showing correct environment variables. I also can't get it to work in firefox, though it does in chrome. (Also works in libreoffice). I can get it working in a urxvt terminal.
As this seems specific to dwl, I *think* it may be an upstream issue, but, while I realize this is an edge usage case, figured I'd ask in case anyone has run into it and solved it. (FWIW, in Fedora, I can't even open urxvt in dwl, with a message of can't open display :0, though it works in Fedora's labwc, but I figure that's a Linux, or more likely, Fedora issue).

