On Sunday 10 February 2008 02:54, Brian G. Peterson wrote:
> Thomas Braun wrote:
> > yes we have made some changes to the syntax highlightning. From your
> > description it looks like the new highlightning breaks at some point.
> > Unfortunately I don't know this noweb documents you mentioned.
> > What file suffixes do these files have?
> usually .nw or .Rnw
> Noweb allows other programming languages to be mixed into a LaTeX
> document. the document is then compiled with one other step before the
> tex compile steps. If you search around, you'll find people's pages on
> using Noweb with Kile or Lyx.
> In my case, this is R (http://www.r-project.org/) statistical code.
> Stand alone program R files would generally have the extension .R, and
> are recognized as "R script" by the KDE syntax highlighting tools.
> > We had also a change in the way
> > some documents are handled.
> > It would be best if you provide a small complete testcase.
> Noweb scripts are always called out in code blocks
> code line
> code line$var
> output LaTeX
> The block above, if pasted into kile 2.x, should demonstrate the
> problem. Take any LaTeX file, drop this in somewhere near the beginning.
The behaviour is the same for 1.9.3 and 2.0 so this is not a regression.
Have a try with the attached syntax file, it should do the trick as quick
And about changing the syntax to some other language. How do I know to which
language I must change?
> I think, after looking at this more closely, that the issue is
> unbalanced $ characters make Kile think that the equation block is still
> So, for step one of a fix, the LaTeX syntax highlighting file should
> recognize NoWeb blocks of the form
> # and comments
> and simply not parse anything between the <<...>>= and the @
> Ideally, the NoWeb block would be a trigger to change highlighting
> inside the block, but fixing the broken bits first seems to make more
> - Brian
> > It is in principle possible to change the highlightning from one
> > language (latex) to another (noweb) and back. But our syntax file is not
> > something easy to play with.
> > Thanks,
> > Thomas
> >> I do most of my writing in noweb documents, and previously, these were
> >> handled reasonably well in Kile 1.9.3
> >> I just upgraded to Kile 2.0, and my noweb files are now very difficult
> >> to work with because of changes in the highlighting code.
> >> Previously, any code between the beginning of a NoWeb block something
> >> like this:
> >> <<SomeName,echo=F>>=
> >> and the end of the block with a single @ symbol on a line by itself
> >> @
> >> were not highlighted at all.
> >> In Kile 2.0, it seems that any $ symbol inside a noweb block throws off
> >> all the highlighting for the rest of the text.
> >> I would greatly appreciate any assistance in either a> making sure that
> >> text between the beginning and end of a NoWeb block isn't highlighted,
> >> or b> somehow telling Kile (or the appropriate syntax file) to highlight
> >> the code inside a NoWeb block using the appropriate syntax highlighting.
> >> I think that I need the answer to a> to get to an answer for option b>,
> >> because once the insides of the block can be handled differently, then
> >> highlighting from some other language could be inserted inside the block
> >> (in my case R script r-project.org)
> >> Thanks for any pointers,