Hi,

I've noticed something strange in xterm properties configuration. I
don't know in fact how many versions ago this organisation was
designed (at least 9.x).

There is two configuration files in /etc/X11/app-defaults for the
application : XTerm and XTerm-color.

In XTerm-color, I read : *#include "XTerm"*. Okay.

By putting my preferences (white on black :-)) on XTerm-color, i
didn't see my editions taking effect.

But if i put theses in XTerm file, or, cleaner way, move *#include
"XTerm"* from XTerm-color into XTerm as *#include "XTerm-color"*, it
works.

Is this a bad organisation, or did I make something wrong ?

Regards,

--
Mounir.

Mounir <downwater@gmail.com> wrote:

> But if i put theses in XTerm file, or, cleaner way, move *#include
> "XTerm"* from XTerm-color into XTerm as *#include "XTerm-color"*, it
> works.

see the note in xterm's manpage regarding

*customization: -color

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

> see the note in xterm's manpage regarding
> *customization: -color

Okay :

> /usr/lib/X11/app-defaults/XTerm
> the xterm default application resources.
> /usr/lib/X11/app-defaults/XTerm-color
> the xterm color application resources.
> If your display supports color, use
> this *customization: -color in your
> .Xdefaults file to automatically turn on
> color in xterm and similar applications.

Note about the purpose of these two files. But, my message was about
the "#include" preprocessor command place and syntax.

Regards,

--
Mounir.

Mounir <downwater@gmail.com> wrote:
>> see the note in xterm's manpage regarding
>> *customization: -color

> Okay :

>> /usr/lib/X11/app-defaults/XTerm
>> the xterm default application resources.
>> /usr/lib/X11/app-defaults/XTerm-color
>> the xterm color application resources.
>> If your display supports color, use
>> this *customization: -color in your
>> .Xdefaults file to automatically turn on
>> color in xterm and similar applications.

> Note about the purpose of these two files. But, my message was about
> the "#include" preprocessor command place and syntax.

The message was stating that you did not understand why the colors
worked when pasting the contents of XTerm-color into XTerm, but
not otherwise. That's because the preprocessor looks for XTerm-color
if you supply the given customization.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

> The message was stating that you did not understand why the colors
> worked when pasting the contents of XTerm-color into XTerm, but
> not otherwise. That's because the preprocessor looks for XTerm-color
> if you supply the given customization.

Ok, I might have been uncomprehensible (bad awakening, bad
english :-)).

*Slackware app-default organization* : XTerm-color <- #include"XTerm"
=> It doesn't work (setting colors are not displayed)

After edit : XTerm <- #include "XTerm-color"
=> It works.

So, I wonder if this is not a slackware problem (default
organization). Right ?

Regards,

--
Mounir.

Mounir wrote:
>> The message was stating that you did not understand why the colors
>> worked when pasting the contents of XTerm-color into XTerm, but
>> not otherwise. That's because the preprocessor looks for XTerm-color
>> if you supply the given customization.
>
> Ok, I might have been uncomprehensible (bad awakening, bad
> english :-)).
>
> *Slackware app-default organization* : XTerm-color <- #include"XTerm"
> => It doesn't work (setting colors are not displayed)
>
> After edit : XTerm <- #include "XTerm-color"
> => It works.
>
> So, I wonder if this is not a slackware problem (default
> organization). Right ?

Wrong. Put

*customization: -color

in your ~/.Xdefaults (create the file if it doesn't already exist). Then run

xrdb -merge ~/.Xdefaults

or you can restart your x server. Then start a new xterm. The settings
from XTerm-color will now be in effect. Without the *customization line
in your .Xdefaults, xterm will not know to look at the XTerm-color file
and will only load the XTerm file.

Steve

On 15 fév, 13:32, Steven J Masta <sma...@earthlink.net> wrote:
> Mounir wrote:
> >> The message was stating that you did not understand why the colors
> >> worked when pasting the contents of XTerm-color into XTerm, but
> >> not otherwise. That's because the preprocessor looks for XTerm-color
> >> if you supply the given customization.
>
> > Ok, I might have been uncomprehensible (bad awakening, bad
> > english :-)).
>
> > *Slackware app-default organization* : XTerm-color <- #include"XTerm"
> > => It doesn't work (setting colors are not displayed)
>
> > After edit : XTerm <- #include "XTerm-color"
> > => It works.
>
> > So, I wonder if this is not a slackware problem (default
> > organization). Right ?
>
> Wrong. Put
>
> *customization: -color
>
> in your ~/.Xdefaults (create the file if it doesn't already exist). Then run
>
> xrdb -merge ~/.Xdefaults
>
> or you can restart your x server. Then start a new xterm. The settings
> from XTerm-color will now be in effect. Without the *customization line
> in your .Xdefaults, xterm will not know to look at the XTerm-color file
> and will only load the XTerm file.
>
> Steve

Thanks, useful for a later need :-).

When I started the thread, I said I *succeed to set up customized
colors* (by turning *#include "XTerm"* from *app-default/XTerm-color
into app-default/XTerm*), and wondered if this is not an organisation
problem in Slackware distribution to have the *include preprocessor
instruction* in XTerm-color rather than XTerm.

Regards,

--
Mounir.

Mounir <downwater@gmail.com> wrote:

> When I started the thread, I said I *succeed to set up customized
> colors* (by turning *#include "XTerm"* from *app-default/XTerm-color
> into app-default/XTerm*), and wondered if this is not an organisation
> problem in Slackware distribution to have the *include preprocessor
> instruction* in XTerm-color rather than XTerm.

no, it's standard (for xterm).

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

> no, it's standard (for xterm).

0_o ?! Err... Ok, thanks.

Anybody tries to set global color properties without touching this
standard ?

Regards,

--
Mounir.