[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: delphi-other-face mismatch
From: |
Richard M. Stallman |
Subject: |
Re: delphi-other-face mismatch |
Date: |
Mon, 12 Sep 2005 00:57:09 -0400 |
delphi-other-face mismatch
In-Reply-To: <address@hidden>
X-Y-GMX-Trusted: 0
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on monty-python
X-Spam-Level:
X-Spam-Status: No, hits=0.1 required=5.0 tests=RCVD_IN_SORBS autolearn=no
version=2.63
Thanks for the patient explanations.
> If FACE is empty the display engine interprets the semantics of
> FACE
>
> I am not sure what situation you're talking about. Where in the data
> structure was nil encountered?
I needlessly complicated things here. All I wanted to say is that the
display engine handles
(defface face nil
"Nil face.")
(put-text-property (line-beginning-position) (line-end-position) 'face
'face)
and
(put-text-property (line-beginning-position) (line-end-position) 'face nil)
much the same way.
In that case, maybe the `face' custom type should accept nil
as an alternative. That way, the existing default for
delphi-other-face would be valid, it would still work the same
as now, and it would not require changing the :type spec.
Does anyone see any problems with that?