Re: postscript monochrome and specified color

[<tim...@en...>]

Daniel J Sebald wrote:
> Ethan A Merritt wrote:
>  =20
>>
>> If you ask for default dashed lines via "set term post dashed"
>> that doesn't stop you from explicitly drawing a solid line.
>>
>> If you ask for a small default font via "set term post font 'Times' 4"
>> that doesn't stop you from explicitly writing labels in a larger font.
>>
>> If you ask for default thick lines via 'set term post lw 5'
>> that doesn't stop you from explicitly drawing a thin line.
>>
>> So if you ask for default black lines via 'set term post mono',
>> why should it stop you from explicitly drawing a blue line?
>>    =20
>
> Because term property "monochrome" outranks other colors in the chess g=
ame of display mediums, I don't know.  None of those other defaults are t=
erm properties.
>  =20
That's where the ambiguity comes from.  As they are options to 'set=20
term', I would tend to agree with Daniel. If you ask the terminal to=20
output in monochrome, you expect everything to be in monochrome.

However, if the above options could be handled by the core, via a=20
command 'set default' for example, then Ethan's described behaviour=20
makes much more sense.

Ex : 'set default dashed font "Times,4" lw 5 mono' would not prevent=20
from override them in particular labels, lines, or whatever.

Implementing these options in the core seems reasonable, not that hard,=20
and would save a lot of code duplication in the terminals. One more=20
thing on my post-4.2 projects list.

Best regards,

Timoth=E9e