Re: guidance for making a .Xresources file.
On Wed, Feb 09, 2011 at 01:28:53PM EST, Bob Proulx wrote:
> Chris Jones wrote:
> > That's odd.. the vnc4server script on ‘lenny’ from the vnc4server
> > package tests the existence of the file:
> > [ -r ~/.Xresources ] && xrdb -merge ...
> The vncserver uses the alternatives. It could be one of several
> different servers. From my machine:
> $ update-alternatives --display vncserver
> vncserver - auto mode
> link currently points to /usr/bin/tightvncserver
> /usr/bin/tightvncserver - priority 70
> slave vncconnect: /usr/bin/tightvncconnect
> slave vncconnect.1.gz: /usr/share/man/man1/tightvncconnect.1.gz
> slave vncserver.1.gz: /usr/share/man/man1/tightvncserver.1.gz
> Current 'best' version is '/usr/bin/tightvncserver'.
> The tightvncserver package says:
> Creating default startup script /home/bob/.vnc/xstartup
> And that file is:
> xrdb $HOME/.Xresources
> xsetroot -solid grey
> #x-terminal-emulator -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> #x-window-manager &
> # Fix to make GNOME work
> export XKL_XMODMAP_DISABLE=1
> But undoubtedly other vnc servers create different files there. :-)
Ah, yes.. I'm unclear as to how I got to have vnc4server and
tightvncserver both installed on my machine. :-)
Now the problem is that I use the old, possibly deprecated, ~/.Xdefaults
and I have a lot of stuff in there. Since I was in a rush and testing
something unrelated, when I saw that I was gettting the wrong fonts,
colors, etc. etc. I just duplicated did: cp .Xdefaults .Xresources.
That's what gave me the idea of the empty ~/.Xresources file.
But since debian systems also have tons of X system-wide resources in
/etc/X11/app-defaults/*, I think I should keep that in mind, and check
whether whatever vnc server I'm running is aware of those.. or maybe
they're picked up by default anyway and I shouldn't worry about it.