候选词会默认选中光标所在位置的词语 #1167
Comments
|
经测试，设置了以下环境变量之后这个问题就没再出现了： 但是根据fcitx5的文档，Plasma Wayland上是不需要这两个变量的，不知道是不是Plasma6的原因。 |
wengxt
added a commit
that referenced
this issue
Nov 3, 2024
|
是界面的代码问题。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
输入中文时，如果光标恰好停留在候选词面板非第一个词的位置，会导致自动高亮选中光标所在位置的词，但是实际按Space输入的还是默认的第一个候选词，而且后续的输入会一直高亮选中第一次光标所在位置的词语，同时用键盘选择候选词的快捷键(
Tab和Shift+Tab)会失效，只能用鼠标选择一次并输入之后才能生效。这个bug不影响正常输入，只是高亮位置错误，容易引起误输入。
Steps to Reproduce
Expected Behavior
候选词面板应该高亮第一个词语，而不是鼠标所在位置的词语，除非用户再次移动鼠标，再跟随鼠标进行高亮
Output of fcitx5-diagnose command
System Info:
uname -a:lsb_release -a:lsb_release -d:/etc/lsb-release:/etc/lsb-releasenot found./etc/os-release:Desktop Environment:
Desktop environment is
kde.XDG SESSION TYPE:
Bash Version:
Environment:
DISPLAY:
Keyboard Layout:
setxkbmap:xprop:Locale:
All locales:
Current locale:
Directories:
Home:
${XDG_CONFIG_HOME}:Environment variable
XDG_CONFIG_HOMEis not set.Current value of
XDG_CONFIG_HOMEis~/.config(/home/xx/.config).Fcitx5 Settings Directory:
Current fcitx5 settings directory is
~/.config/fcitx5(/home/xx/.config/fcitx5).Current user:
The script is run as xx (1000).
Fcitx State:
executable:
Found fcitx5 at
/usr/bin/fcitx5.version:
Fcitx version:
5.1.11process:
Found 2 fcitx5 processes:
fcitx5-remote:fcitx5-remoteworks properly.DBus interface:
Using
dbus-sendto check dbus.Owner of DBus name
org.fcitx.Fcitx5is:1.37.PID of DBus name
org.fcitx.Fcitx5owner is1869.Debug information from dbus:
Fcitx Configure UI:
Config Tool Wrapper:
Found fcitx5-configtool at
/usr/bin/fcitx5-configtool.Config GUI for qt:
Found
fcitx5-config-qtat/usr/bin/fcitx5-config-qt.Config GUI for kde:
kcmshell5not found.Frontends setup:
The environment variable checked by this script only shows the environment under current shell. It is still possible that you did not set the environment to the whole graphic desktop session. You may inspect the actual environment variable of a certain process by using
xargs -0 -L1 /proc/$PID/environfor a certain process that you find not working.Xim:
${XMODIFIERS}:Environment variable XMODIFIERS is "@im=fcitx5" instead of "@im=fcitx". Please check if you have exported it incorrectly in any of your init files.
Please set environment variable XMODIFIERS to "@im=fcitx" using the tool your distribution provides or add
export XMODIFIERS=@im=fcitxto your~/.xprofile. See Input Method Related Environment Variables: XMODIFIERS.Xim Server Name from Environment variable is fcitx5.
XIM_SERVERS on root window:
Xim server name: "ibus" is different from that set in the environment variable: "fcitx5".
XIM for Emacs:
Your LC_CTYPE is set to C instead of one of zh, ja, ko. You may not be able to use input method in emacs because of an really old emacs bug that upstream refuse to fix for years.
XIM encoding:
Your LC_CTYPE is set to C whose encoding is not UTF-8. You may have trouble committing strings using XIM.
Qt:
qt4 -
${QT4_IM_MODULE}:Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add
export QT_IM_MODULE=fcitxto your~/.xprofile. See Input Method Related Environment Variables: QT_IM_MODULE.fcitx5-qt4-immodule-probingnot found.qt5 -
${QT_IM_MODULE}:Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add
export QT_IM_MODULE=fcitxto your~/.xprofile. See Input Method Related Environment Variables: QT_IM_MODULE.It is OK to use qt5 built-in Wayland im module if your compositor fully supports text-input protocol used by qt5.
Using fcitx5-qt5-immodule-probing to check the actual im module to be used under current environment:
qt6 -
${QT_IM_MODULE}:Please set environment variable QT_IM_MODULE to "fcitx" using the tool your distribution provides or add
export QT_IM_MODULE=fcitxto your~/.xprofile. See Input Method Related Environment Variables: QT_IM_MODULE.It is OK to use qt6 built-in Wayland im module if your compositor fully supports text-input protocol used by qt6.
Using fcitx5-qt6-immodule-probing to check the actual im module to be used under current environment:
Qt IM module files:
Found fcitx5 qt6 module:
/lib64/fcitx5/qt6/libfcitx-quickphrase-editor5.so.Found fcitx5 qt5 module:
/lib64/fcitx5/qt5/libfcitx-quickphrase-editor5.so.Found fcitx5 im module for qt6:
/lib64/qt6/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.Found fcitx5 im module for qt5:
/lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so.Following error may not be accurate because guessing Qt version from path depends on how your distribution packages Qt. It is not a critical error if you do not use any Qt application with certain version of Qt or you are using text-input support by Qt under Wayland.
Cannot find fcitx5 input method module for Qt4.
Gtk:
gtk -
${GTK_IM_MODULE}:Please set environment variable GTK_IM_MODULE to "fcitx" using the tool your distribution provides or add
export GTK_IM_MODULE=fcitxto your~/.xprofile. See Input Method Related Environment Variables: GTK_IM_MODULE.It is OK to use gtk built-in Wayland im module if your compositor fully supports text-input protocol used by gtk.
Using fcitx5-gtk2-immodule-probing to check the actual im module to be used under current environment:
Using fcitx5-gtk3-immodule-probing to check the actual im module to be used under current environment:
Using fcitx5-gtk4-immodule-probing to check the actual im module to be used under current environment:
gtk-query-immodules:gtk 2:
Found
gtk-query-immodulesfor gtk2.24.33at/usr/bin/gtk-query-immodules-2.0-64.Version Line:
Found fcitx5 im modules for gtk
2.24.33.gtk 3:
Found
gtk-query-immodulesfor gtk3.24.43at/usr/bin/gtk-query-immodules-3.0-64.Version Line:
Found fcitx5 im modules for gtk
3.24.43.Gtk IM module cache:
gtk 2:
Found immodules cache for gtk
2.24.33at/lib64/gtk-2.0/2.10.0/immodules.cache.Version Line:
Found fcitx5 im modules for gtk
2.24.33.gtk 3:
Found immodules cache for gtk
3.24.43at/lib64/gtk-3.0/3.0.0/immodules.cache.Version Line:
Found fcitx5 im modules for gtk
3.24.43.Gtk IM module files:
gtk 2:
All found Gtk 2 immodule files exist.
gtk 3:
All found Gtk 3 immodule files exist.
gtk 4:
All found Gtk 4 immodule files exist.
Configuration:
Fcitx Addons:
Addon Config Dir:
Found fcitx5 addon config directory:
/usr/share/fcitx5/addon.Addon List:
Found 29 enabled addons:
Found 0 disabled addons:
Addon Libraries:
All libraries for all addons are found.
User Interface:
Found 3 enabled user interface addons:
Input Methods:
/home/xx/.config/fcitx5/profile:Log:
date:/home/xx/.config/fcitx5/crash.log:/home/xx/.config/fcitx5/crash.lognot found.Warning: the output of fcitx5-diagnose contains sensitive information, including the distribution name, kernel version, name of currently running programs, etc.
Though such information can be helpful to developers for diagnostic purpose, please double check and remove as necessary before posting it online publicly.
The text was updated successfully, but these errors were encountered: