Re: Global Font Lock by default

[Eli Zaretskii]

> Cc: address@hidden
> From: Dan Nicolaescu <address@hidden>
> Date: Tue, 01 Nov 2005 21:46:43 -0800
> 
> Eli Zaretskii <address@hidden> writes:
> 
>   > > For example: on a 256 colors xterm, what should list-colors-display
>   > > show when using --color=8? The same as it would on a 8 color xterm
>   > > (and no --color options)?
>   > 
>   > Yes.
> 
> That does not happen right now. The problem is that
> xterm-register-default-colors creates (display-color-cells) colors, it
> does not take into account the --color parameter.

That's very strange, because the code was designed so that
display-color-cells _does_ take --colors into account.  Here's how it
was supposed to work:

  . display-color-cells calls tty-display-color-cells

  . tty-display-color-cells returns the value of TN_max_colors

  . TN_max_colors is modified by term.c:tty_setup_colors

  . tty_setup_colors is called by frame.c:store_frame_param (via
    set_tty_color_mode) when the frame parameters alist includes the
    tty-color-mode parameter

  . When Emacs is invoked with --colors=MODE, the startup code (in
    tty-handle-args) pushes the appropriate tty-color-mode parameter
    into the alist

Which part of this isn't working, and why?

> This can be fixed either in xterm-register-default-colors or in
> display-color-cells.  What is the preferable fix?

I cannot answer this without understanding the problem.  The fix
should be where the bug lurks, in general.