Fbterm - Revision history

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:54:06Z

Text replacement - "<translate1>" to "<translate>"

← Older revision		Revision as of 22:54, 2 February 2016
Line 1:		Line 1:
	<languages/>		<languages/>

	<~~translate1~~>		<translate>
	<!--T:1-->		<!--T:1-->
	{{infobox tool		{{infobox tool

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:53:43Z

Text replacement - "<translate>" to "<translate1>"

← Older revision		Revision as of 22:53, 2 February 2016
Line 1:		Line 1:
	<languages/>		<languages/>

	<~~translate~~>		<translate1>
	<!--T:1-->		<!--T:1-->
	{{infobox tool		{{infobox tool

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:52:29Z

Text replacement - "<languages1/>" to "<languages/>"

← Older revision		Revision as of 22:52, 2 February 2016
Line 1:		Line 1:
	<~~languages1~~/>		<languages/>

	<translate>		<translate>

Weng Xuetian: Text replacement - "" to ""

2016-02-02T22:51:55Z

Text replacement - "<languages/>" to "<languages1/>"

← Older revision		Revision as of 22:51, 2 February 2016
Line 1:		Line 1:
	<~~languages~~/>		<languages1/>

	<translate>		<translate>

Weng Xuetian: 15 revisions imported

2016-02-02T22:43:07Z

15 revisions imported

← Older revision	Revision as of 22:43, 2 February 2016
(No difference)

Weng Xuetian: Text replacement - "" to ""

2016-01-25T21:26:35Z

Text replacement - "<languages />" to "<languages/>"

← Older revision		Revision as of 21:26, 25 January 2016
Line 1:		Line 1:
	<languages />		<languages/>

	<translate>		<translate>

Weng Xuetian: /* When fcitx is already running under X */

2013-05-16T16:59:54Z

When fcitx is already running under X

← Older revision		Revision as of 16:59, 16 May 2013
Line 48:		Line 48:
	fcitx-fbterm-helper		fcitx-fbterm-helper

	To start fbterm. If your display is not 0, you can use		To start fbterm. If your display is not 0, for example, it's running as :1, you can use

	fcitx-fbterm-helper -d ~~[display nunmber]~~		fcitx-fbterm-helper -d 1

	to override it.		to override it.

Weng Xuetian at 16:59, 16 May 2013

2013-05-16T16:59:25Z

← Older revision		Revision as of 16:59, 16 May 2013
Line 7:		Line 7:
	\|screenshot = [[File:fcitx-fbterm.png\|200px]]		\|screenshot = [[File:fcitx-fbterm.png\|200px]]
	\|caption2 = fbterm support for fcitx		\|caption2 = fbterm support for fcitx
	\|version = 0.1.3		\|version = 0.2.0
	\|programming language = C		\|programming language = C
	\|dependency = fbterm		\|dependency = fbterm
Line 16:		Line 16:
	== Intro == <!--T:2-->		== Intro == <!--T:2-->
	Let you use fcitx under [http://code.google.com/p/fbterm/ fbterm].		Let you use fcitx under [http://code.google.com/p/fbterm/ fbterm].

			This wiki page is written for fcitx-fbterm 0.2.0 or higher.

	== Prepare == <!--T:3-->		== Prepare == <!--T:3-->
Line 35:		Line 37:
	sudo chmod u+s /usr/bin/fbterm		sudo chmod u+s /usr/bin/fbterm

	~~== Launch fbterm ==~~ <!--T:7-->		<!--T:7-->
	Notice, if you don't use KMS (Kernel mode settings, in other words, open source display driver), you must start fbterm with root.		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 === <!--T:15-->		=== When fcitx is already running under X === <!--T:15-->
	For example, if your X is :0 (this is the default case for desktop user).		For example, if your X is :0 (this is the default case for desktop user).

			You can use

	<!--T:8-->		<!--T:8-->
	fcitx-fbterm-helper -d 0		fcitx-fbterm-helper

			To start fbterm. If your display is not 0, you can use

			fcitx-fbterm-helper -d [display nunmber]

			to override it.

	<!--T:9-->		<!--T:9-->
	If there is no error ~~output~~, it should work.		If there is no error, then everything should work, one additional thing you need pay attention is, fbterm hardcodes Ctrl+Space as input method trigger key, this is not controlled by fcitx and not changable.

	=== Without X or have problem === <!--T:10-->		=== Without X or have some problem === <!--T:10-->
	fcitx-fbterm-helper -l		fcitx-fbterm-helper -l

	<!--T:11-->		<!--T:11-->
	It will launch ~~a new dbus daemon and~~ new fcitx. ~~There is a message indicating that there should~~ be ~~only fcitx running~~. ~~So run~~		It will launch new fcitx. And fcitx will be killed when fbterm ends.

	<!--~~T:12-->~~		If there is already a fcitx running, fcitx-fbterm-helper will refuse to work, you can use
	~~killall fcitx~~

	~~<!--T:13-->~~		killall fcitx
	~~before you start execute~~ fcitx~~-fbterm-helper.~~

	~~<!--T:14-->~~		to kill existing fcitx.
	~~Unreleased fcitx-fbterm 0.1.4's fcitx-fbterm-helper can~~ kill ~~dbus-daemon and fcitx when fbterm quits, you can grab the script [https://github.com/fcitx/fcitx-fbterm/blob/master/scripts/~~fcitx~~-fbterm-helper here]. It's ok to run it from anywhere so you don't need to replace the system script~~.

	== ~~Trouble~~ == <!--T:16-->		== Troubleshoot == <!--T:16-->
	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.		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.

	</translate>		</translate>

Weng Xuetian: /* With X running, and run as same user with X */

2013-05-16T16:48:13Z

With X running, and run as same user with X

← Older revision		Revision as of 16:48, 16 May 2013
Line 42:		Line 42:

	<!--T:8-->		<!--T:8-->
	~~export DISPLAY=:0~~		fcitx-fbterm-helper -d 0
	fcitx-fbterm-helper

	<!--T:9-->		<!--T:9-->

Weng Xuetian: /* Prepare */

2013-05-16T16:47:00Z

Prepare

← Older revision		Revision as of 16:47, 16 May 2013
Line 30:		Line 30:

	<!--T:5-->		<!--T:5-->
	or		or (it's NOT safe because it sets setuid.)

	<!--T:6-->		<!--T:6-->
	sudo chmod u+s /usr/bin/fbterm ~~# not-safe because of it set setuid.~~		sudo chmod u+s /usr/bin/fbterm

	== Launch fbterm == <!--T:7-->		== Launch fbterm == <!--T:7-->