[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: Feature request: include syntax highlighting rules from modeline
From:       Matthew Woehlke <mwoehlke () tibco ! com>
Date:       2006-10-30 22:24:23
Message-ID: ei5u2o$225$1 () sea ! gmane ! org
[Download RAW message or body]

Anders Lund wrote:
> On Monday 30 October 2006 19:43, Matthew Woehlke wrote:
>> Does this mean KATE4 will be able to do things like highlight here-docs
>> in bash scripts? 
> 
> No. Not unless you write a bash hl file that assumes some HERE delimiter that 
> tells the highlighter what to import ( << END_HTML; ), and jumps context. And 
> you can do that now.

Oh, ok, I think I see where I mis-read. You are saying that I can do 
some 'sneaky' things to the context I am including, not dynamically 
choose a context to include? That makes sense, sounds useful, etc. (And 
this WILL include the ability to include arbitrary sub-contexts from a 
particular .xml, ala http://bugs.kde.org/show_bug.cgi?id=135844, right?)

(Note: snipping what I replied to not the best idea, I had to go back 
and look at a different message to realize how I had mis-read.)

>> That would be very useful! It would be nice if there 
>> was a way to tint the background color, though, so you could tell such
>> highlighting apart from the upper-level highlighting. (I don't think
>> overriding the colors as we currently do with <IncludeRules/> would
>> work, since I assume we are talking about arbitrary highlighters rather
>> than pre-defined sets.)
> 
> I do not understand that sentence. We do absolutely nothing to override 
> colors.

Well, yeah, because you're not doing what I thought you were above. So 
this entire train of thought makes no sense and should be disregarded. :-)

>> This brings up another wish that I had tried to code at one point and
>> couldn't get to work right: color inheritance. I.e. it would be really
>> nice if highlighters like C/C++ could use the colors specified for the
>> Doxygen highlighter as "default" rather than just 'dsXyz' (did that make
>> any sense?).
> 
> No.
> 
> Doxygen text in C++ files use the doxygen colors pr default. But you have the 
> option to change them. That said, I never checked if changing the colors for 
> doxygen is correctly utilized.

What I want is this:
Let's say I go to settings->colors->highlighting and select 
'Markup/Doxygen'. I then make "Doxygen->Words" dark purple. Now if I go 
to 'Sources/C++' and check 'use default' for "Doxygen->Words", I would 
like it to use the dark purple I set above. Instead I get the default 
for 'dsKeyword'. Is that less cryptic? :-)

This seems like an obvious improvement; let the user set colors for 
(e.g.) Doxygen in one place (Markup/Doxygen) and all .xml's (e.g. C, 
C++, etc) that <IncludeRules/> that particular highlighter will pick up 
the user-specified colors. Right now one has to manually set the colors 
for each highlighter that includes whatever other highlighter.

Removing the ability to override is obviously a bad idea, but 
inheritance would be nice.

-- 
Matthew
This message will self destruct in ten centuries.

_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]