On Mon, Jun 23, 2003 at 03:32:19PM +0200, Lucio wrote:
> Alle 15:05, lunedi 23 giugno 2003,immerso nell'esegesi delle monadi di
> Leibniz, fui distratto da Hugh Hartmann che proclamo':
Ciao Lucius,
gia' il nome (latino) mi ispira (ma perche' immergersi in Leibniz e non
sulle equazioni di Maxwell o nelle serie di Fourier?)
[...]
> > La cosa migliore che puoi fare. se non vuoi aggiungere l'opzione
> > -geomerty a un comando riferito a un'applicazione in .twmrc, e' quella
> > di crearti (se non l'hai gia') il file .Xresources utilizzando i file
> > presenti in /usr/lib/X11/app-default/, che rapressentano i file-risorse
> > di ogni applicazione di xwindow. Cioe' fai un "merge" dei file delle
> > applicazioni che usi maggiormente per esempio con cat: ....
[...]
> Io non vorrei dire una gran stupidata, forse non ho capito bene il tuo
> problema, ma non sarebbe molto piu' semplice (sicuramente molto, molto
> piu' sporco), crearti degli alias in .bashrc dei programmi che ti
> interessano, mettendoci dentro l'opzione --geometry.
Ma questo povero file .bashrc o (piu' vecchio) bash_profile gia' contiene un
sacco di alias e variabili d'ambiente perche' continuare a riempirlo? :-)
Questo e' il momento giusto per esplorare il file di configurazione dei vari
window manager: .twmrc, .ctwmrc, .fvwmrc, .fvwm2rc, .icewmrc, .steprc, ecc,
ecc .. :-)
In fondo e' consigliato dalla Debian stessa di usare i file presenti in:
/usr/lib/X11/app-defaults/ per "customizzare" il proprio ambiente Xwindow,
dalle FAQ Debian:
_________________________________________________________________
The Debian GNU/Linux FAQ
Capitolo 10 - Personalizzare la propria installazione di Debian GNU/Linux
_________________________________________________________________
[cut]
10.4 Come posso configurare i default di un'applicazione del programma X11?
I programmi X di Debian installeranno le loro risorse per le
applicazioni nella directory /etc/X11/app-defaults/. Se si vogliono
personalizzare globalmente le applicazioni X, si mettano le proprie
personalizzazioni in questi file. Sono marcati come file di
configurazione, quindi il loro contenuto sara' preservato durante gli
aggiornamenti.
_________________________________________________________________
[cut]
e dalle FAQ di XFree86 (usr/share/xfree86-common/doc/FAQ o
usr/doc/xfree86-common/FAQ :
[cut]
*) What are X resources?
X clients are typically customizable in their appearance and behavior in a
very large number of ways. It would be very cumbersome to require X clients
to be called with command-line arguments specifying each of the configurable
parameters. Therefore, the X server maintains a database of X resources.
When an X client connects to an X server, it inherits a set of properties
from the X server that correspond to it.
The strength of X resources is at the same time what makes them
intimidating; they are hierarchical and can be as general or as specific as
is desired. Almost all X clients, for example, recognize resources called
"foreground" and "background", and if the X server contains an appropriately
general resource for these properties, every X client that recognizes them
will use them.
*) What are app-defaults?
Application defaults files ("app-defaults") are essentially a way of
externalizing an X client's configurable parameters' defaults outside the
client binary, so that they can be changed without recompiling the client.
App-defaults files are mostly, but not exclusively, used by X clients
written using the Xt (X Toolkit Intrinsics) library. On Debian systems they
can be found in /etc/X11/app-defaults (or a localized subdirectory of
/etc/X11).
App-defaults are specified using a class/instance syntax and look very
similar to X resource files (see next question), but there are three very
important differences between app-defaults and X resources:
1) A client's app-defaults are generally essential for its useful operation,
whereas X resources are always optional. In other words, you should be
able to use an X client without specifying any X resources for it, but
if you delete a client's app-defaults file, it may not be usable.
2) App-defaults implicitly bind to the class name specified in the file
name of the app-defaults file. In other words, if I have an
app-defaults file called "Foo", which contains the line:
*Menu*background: red
then this is interpreted as "Foo*Menu*background: red". This is unlike
X resources, where a leading asterisk will cause a resource to bind
globally to all clients that can resolve the resource name.
3) App-defaults are resolved only the by client, on the machine from which
the client is running. X resources, on the other hand, are stored in
the X server and can affect all clients that connect to that server.
Again, the best way to think of app-defaults is as a set of externalized
default settings for a client. They work as if they were part of the client
binary itself.
[cut]
Penso che questo, per oggi, possa bastare ... :-)
Aurevoire
Hugh Hartmann
