From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: Peter Canning <9cn6w6402@sneakemail.com>
Message-ID: <pan.2004.04.24.04.53.34.208306@sneakemail.com>
Content-Type: text/plain; charset=ISO-8859-1
References: <F6DA782F.2A7CF183@mail.gmail.com>, <969120f4722fd9bdd363136c895b96e8@plan9.ucalgary.ca>
Subject: Re: [9fans] p9 mice
Date: Mon, 26 Apr 2004 08:44:30 +0000
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 6c3de950-eacd-11e9-9e20-41e7f4b1d025

On Fri, 23 Apr 2004 17:21:51 +0000, andrey mirtchovski wrote:

>=20
>> What do you mean by an XWindows resource?
>> Is this different from a command-line option?
>> (Sorry, I know very little about X even now.)
>=20
> basically X resources allow you to circumvent having to supply an
> argument for each little thing you want to execute.  for example, to
> let xterm understand utf8 you can either exec xterm -u8 every time or
> set:
>=20
> 	xterm*utf8: 1
>=20
> in .Xresource...
>=20

I think of X resources as Xserver-side environments variables.  Typically
the resources in $HOME/.Xresources get loaded into the X server as
properties of the root window during session startup, so that they are
accessible to X programs using that display no matter where the
program is running.

	- Peter Canning