Fbterm
Version | 0.1.3 |
---|---|
Dependency | fbterm |
Written In | C |
License | GPLv2 |
Website | http://github.com/fcitx/fcitx-fbterm |
Intro
Let you use fcitx under fbterm.
Prepare
Make fbterm can use input method.
sudo setcap 'cap_sys_tty_config+ep' /usr/bin/fbterm
or
sudo chmod u+s /usr/bin/fbterm
Launch fbterm
Notice, if you don't use KMS (Kernel mode settings, in other words, open source display driver), you must start fbterm with root.
With X running, and run as same user with X
For example, if your X is :0 (by default, if you only have one X server).
export DISPLAY=:0 fcitx-fbterm-helper
If no error output, it will work.
Without X or have problem
fcitx-fbterm-helper -l
It will launch a new dbus daemon and new fcitx. There is a message indicating that there should be only fcitx running. So run
killall fcitx
before you start execute fcitx-fbterm-helper.
Unreleased fcitx-fbterm 0.1.4's fcitx-fbterm-helper can kill dbus-daemon and fcitx when fbterm quits, you can grab the script here. It's ok to run it from anywhere so you don't need to replace the system script.
Trouble
If you meet some trouble about keyboard not reaction, screen artifacts, you can first try Ctrl+Alt+E (force fbterm to exit), if this doesn't work and you have enabled magic key (sysctl, kernel.sysrq = 1), you can try only sysrq + r (not the full reisub!), this will force keyboard input to forward to kernel, then you can switch between tty.