Fcitx5: Difference between revisions
imported>Tamiyo add troublshooting steps for wm |
imported>Tamiyo additional clarity around add-ons not detected |
||
| Line 16: | Line 16: | ||
== Troubleshooting == | == Troubleshooting == | ||
=== Add-ons Not Detected === | === Add-ons Not Detected === | ||
Installing fcitx5 using <code>environment.systemPackages</code> can interfere with add-on detection. | Installing fcitx5 using <code>environment.systemPackages</code> can interfere with add-on detection. Make sure to only add fcitx5 to your config as show in [[Fcitx5#Setup | Setup]]. | ||
=== Fcitx5 Doesn't Start When Using WM === | === Fcitx5 Doesn't Start When Using WM === | ||
Revision as of 18:08, 3 January 2024
Fcitx5 is a lightweight input method framework with addon support.
Setup
The following is a simple NixOs configuration that'll setup fcitx5, its GUI config tool, and two addons.
i18n.inputMethod = {
enabled = "fcitx5";
fcitx5.addons = with pkgs; [
fcitx5-mozc
fcitx5-gtk
];
};
Notably, NixOs automagically sets session variables that are required for fcitx5.
Troubleshooting
Add-ons Not Detected
Installing fcitx5 using environment.systemPackages can interfere with add-on detection. Make sure to only add fcitx5 to your config as show in Setup.
Fcitx5 Doesn't Start When Using WM
As of NixOS 23.11 i18n.inputMethod.enabled no longer creates systemd services for fcitx5. Instead it relies on XDG autostart files. If using a Window Manager (WM), such as Sway, you may need to add services.xserver.desktopManager.runXdgAutoStartIfNone to your NixOS configuration.
See the NixOS 23.11 Release Notes for more information.