-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Activating Fcitx causes mouse to be constantly selecting #53
Comments
Sorry for replying late. |
Works for me as well with --im xim or --im fcitx xmonad 0.17.1 |
I was able to reproduce this problem, and found the cause of it. |
pkgsrc changes: * make mlconfig.po installed properly (#66) * remove local patches integrated into upstream Upstream changes (noted in doc/en/ReleaseNote): ver 3.9.3 * mlterm-wl supports xdg-decoration. * Add --disable-compact-truecolor option to ./configure script. * Add vte 0.68 API symbols to libvte compatible library. * Add libvterm 0.2 API symbols to libvterm compatible library. * Add --sdpr / simple_scrollbar_dpr option. (arakiken/mlterm#64) * Set "COLORTERM=truecolor" environmental variable. (arakiken/mlterm#36) * Update unicode property table (generated from UnicodeData.txt and EastAsianWidth.txt) to version 15.0.0. * Support mosh-1.4.0. * Merge patches: arakiken/mlterm#45. arakiken/mlterm#46. arakiken/mlterm#48. arakiken/mlterm#49. arakiken/mlterm#55. (Add --role / wm_role option) arakiken/mlterm#57. arakiken/mlterm#61. arakiken/mlterm#62. arakiken/mlterm#63. * Bug fixes: Fix arakiken/mlterm#34. Fix arakiken/mlterm#35. Fix arakiken/mlterm#39. Fix arakiken/mlterm#44. Fix arakiken/mlterm#50. Fix arakiken/mlterm#51. Fix arakiken/mlterm#53. Fix https://twitter.com/isaki68k/status/1555895011991883783. Fix segfault in starting mlterm with --dyncomb and --otl.
Input works normally while Fcitx is inactive. But when I activate Fcitx using Ctrl+Space, MLterm starts treating the mouse as if button 1 was pressed, selecting text whenever I move the cursor.
This is the minimal
.xinitrc
that reproduces the issue for me (I also tested withi3
andstartxfce4
instead ofxmonad
and the issue appeared; it seems to not depend on the window manager):It seems not to depend on the
fcitx
flag either, as the issue also appears when I try a minimal configuration as described in README:This report on the mailing list describes an issue very similar to mine: https://sourceforge.net/p/mlterm/mailman/message/37022073/ However, the report does not mention Fcitx.
The text was updated successfully, but these errors were encountered: