ORACLE XE on Arch Linux

`yaourt -S oracle-xe` got ERROR: oracle-xe-univ-10.2.0.1-1.0.i386.rpm was not found in the build directory and is not a proper URL.

It seem that oracle-xe source was broken in PKGBUILD, fixed by three steps:

1. download oracle-xe-univ-10.2.0.1-1.0.i386.rpm from Oracle website.
2. `Python -m SimpleHTTPServer`.
3. changed the 'source' line in PKGBUILD as : source=(http://localhost:8000/oracle-xe-univ-10.2.0.1-1.0.i386.rpm)

while i=`line`与while read i的区别


a)
while i=`line`
do
echo "i is set to $i"
done < my_file

b)
while read i
do
echo "i is set to $i"
done < my_file

there are a few differences. e.g., try inputting a line
ending with backslash ("\"), such as:

first line \
second line

the read i version reads both lines into one instance of
$i (sans the escaping backslash: "first line second line").
but the `line` version executes twice, first reading the
backslash-ending line (with the backslash) into an instance
of $i ("first line \"), and the second time 'round the loop
the subsequent line into $i ("second line").

another difference: leading spaces/tabs are stripped in
the read i version (at least in some versions of various
shells; i cannot recall if all shells have always done this
or not).

refers to Heiner Steven's unix shell threads

GTK+界面无法激活FCITX

升级ibus至1.1版本后无法启动。运行ibus-setup报以下错误

Traceback (most recent call last):
File "/usr/share/ibus/setup/main.py", line 359, in
Setup().run()
File "/usr/share/ibus/setup/main.py", line 77, in __init__
self.__init_ui()
File "/usr/share/ibus/setup/main.py", line 90, in __init_ui
self.__config = self.__bus.get_config()
AttributeError: 'Bus' object has no attribute 'get_config'

没办法，从fcitx svn上check了源码(3.6.0RC)，打了了一个deb包。安装过程参照了英文Locale下使用中文输入法
, 重启X后, 发现所有的GTK程序无法用激活fcitx, 一番折腾后, 貌似XIM找不到正确的gtk.immodules配置文件引起的。解决办法：
1. gtk-query-immodules-2.0 > ~/.gtk-2.0/gtk.immodules
2. 在.profile文件里增加一行： export GTK_IM_MODULE_FILE=~/.gtk-2.0/gtk.immodules
3. 编辑/etc/X11/Xsession.d/95xinput

#!/bin/bash
export XMODIFIERS="@im=fcitx"
export XIM=fcitx
export XIM_PROGRAM=fcitx
export GTK_IM_MODULE="xim"
export QT_IM_MODULE="xim"
fcitx

4. 注意"xim"大小写要与~/.gtk-2.0/gtk.immodules里一致

从源码编译fcitx的DEB包

sudo apt-get build-dep fcitx
svn checkout http://fcitx.googlecode.com/svn/trunk/ trunk
svn export trunk fcitx
cd fcitx
./autogen.sh
fakeroot dpkg-buildpackage -b

Openbox guide

http://wiki.archlinux.org/index.php/Openbox
http://urukrama.wordpress.com/openbox-guide/

deb http://ppa.launchpad.net/k-belding/ppa/ubuntu intrepid main
deb-src http://ppa.launchpad.net/k-belding/ppa/ubuntu intrepid main

Cairo Composite Manager
http://cairo-compmgr.tuxfamily.org/

今天碰到一个MIME问题，在ROX中(nautilus, thunar中正常)，.doc(MS-Word)被识别被text/plain，导致我在为其他文本文件如.txt设置set run action: xterm -e vi "$@"后，.doc文件也会用vi打开。用MIME-Editor发现text/plain中包含了.doc文件类型。
以'su'编辑/usr/share/mime/globs文件，删除行 text/plain:*.doc
问题就解决了。

XToolkit on Solaris/Linux

Starting with release J2SE^TM 5.0, AWT has been re-implemented on the Solaris and Linux platforms. The new Toolkit implementation provides the following advantages:

• Removes the dependency on Motif and Xt libraries.
• Interoperates better with other GUI Toolkits.
• Provides better performance and quality.

The new Toolkit (XToolkit) is the default on Linux in J2SE 5.0. Solaris will continue to use the MToolkit (Motif-based Toolkit) as the default in J2SE 5.0, but eventually will be replaced with XToolkit.

Explicitly Setting the Toolkit

You can explicitly set the toolkit for an applet or application using an environment variable or a system property. Keep in mind that the environment variable overrides the system property.

• Setting the toolkit for an application:
  • Using an environment variable. This needs to be set before starting the VM.

     csh:
    setenv AWT_TOOLKIT XToolkit #selects the XToolkit
    setenv AWT_TOOLKIT MToolkit #selects the MToolkit
    
    ksh/bash:
    export AWT_TOOLKIT=XToolkit
    export AWT_TOOLKIT=MToolkit
    

  • Using a system property on the command line:

     java -Dawt.toolkit=sun.awt.X11.XToolkit MyApp
    java -Dawt.toolkit=sun.awt.motif.MToolkit MyApp
    

• Setting the toolkit for an applet:
  • Using an environment variable.

    If the browser is started from a terminal window, the environment variable must be set in the terminal window before launching the browser. If the browser is launched from a desktop icon or menu, the toolkit for an applet can't be set using an environment variable. The Java Plug-in Control Panel should be used instead.

  • Using the Plug-in Control Panel:
    • Launch the Java Plug-in Control Panel:

      $java_home/bin/ControlPanel
      

    • Add the system property to the Java Runtime Parameters field under the Advanced tab.

      -Dawt.toolkit=sun.awt.X11.XToolkit
      -Dawt.toolkit=sun.awt.motif.MToolkit