The problem with remote X is bandwidth. This means nice things like pixmap heavy themes and etc are a pain.
remoteXcheck=`echo $DISPLAY | cut -d: -f 1`
if [ -z "$remoteXcheck" ]; then
fbpager&
sonata --hidden&
#pidgin &
ekiga &
autocutsel -fork
zbgset -l
skype&
xcompmgr -d :0.0&
xcompmgr -d :0.1&
remote=""
xhost +127.0.0.1
else
remote=".remote"
export
fi
fluxbox -rc ~/.fluxbox/init$remote
So for a local connection, it will start several apps, set the background and then run fluxbox using the default config, "~/.fluxbox/init". But for a remote connection, it will not run any apps, will not set the background, will tell GTK to use a alternate theme("~/.gtkrc-2.0-remote"), and tell fluxbox to load "~/.fluxbox/init.remote" for it's config.
remoteXcheck=`echo $DISPLAY | cut -d: -f 1`
if [ -z "$remoteXcheck" ]; then
fbpager&
sonata --hidden&
#pidgin &
ekiga &
autocutsel -fork
zbgset -l
skype&
xcompmgr -d :0.0&
xcompmgr -d :0.1&
remote=""
xhost +127.0.0.1
else
remote=".remote"
export
GTK2_RC_FILES="~/.gtkrc-2.0-remote"fi
fluxbox -rc ~/.fluxbox/init$remote
So for a local connection, it will start several apps, set the background and then run fluxbox using the default config, "~/.fluxbox/init". But for a remote connection, it will not run any apps, will not set the background, will tell GTK to use a alternate theme("~/.gtkrc-2.0-remote"), and tell fluxbox to load "~/.fluxbox/init.remote" for it's config.