Hi Michael,<br><br>I can also confirm this occurs on my Vim 7.0 (I'm also running Edgy Eft).<br>Notably it (the red highlight on _ and loss of syntax highlighting) only seems to occur when there is a \section (or sub) command within the .lhs (I am also using lhs2tex). Hadn't noticed this before as I tend not to place sectioning commands in the .lhs and use a main .tex containing sequences like:
<br><br>\subsection{Module foo}<br>\include{foo}<br><br>Not sure if this is present in the Feisty Fawn binaries, I guess someone should file a bug report? :)<br><br>Dave,<br><br><div><span class="gmail_quote">On 05/06/07,
<b class="gmail_sendername">Michael T. Richter</b> <<a href="mailto:ttmrichter@gmail.com">ttmrichter@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
I've given up on getting a decent text editor for editing Haskell (specifically literate Haskell -- plain Haskell works fine in GEDIT). Instead I fire up VIM and get ... a total mess. At first I think maybe I've screwed up a whole bunch of settings or something, so I nuke everything in my home directory that begins with .vim and then, for added measure, head over to /usr/share and nuke the entire ./vim directory tree. I then reinstall vim (from the Ubuntu Edgy archives) to get a brand new set of config files unsullied by my hands.
<br>
<br>
I still get a dog's breakfast.<br>
<br>
A screen shot of what I'm seeing with a representative example of a .lhs file to show what I mean can be found at <a href="http://img357.imageshack.us/img357/5798/gvimexamplezv4.png" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://img357.imageshack.us/img357/5798/gvimexamplezv4.png</a>. (I've pared it down to the minimum I could find that shows the behaviour clearly.) The problems I'm seeing are the ugly white-on-red for underlines, the lack of any kind of differentiation for keywords/operators/etc. vs. identifiers (although
<b>some</b> punctuation is recognized, specifically curly braces), comments not being noted, etc. Basically it looks like the Haskell is simply not being recognized at all (and, if the @saBinds@ thing is what I think it is, it looks like some latex isn't being recognized fully either).
<br>
<br>
Can anybody vim-centric please take a look at this and give me a few educated guesses as to what is happening here? For good measure, here's the beginning of the lhaskell.vim file that comes with my vim distribution (
7.0 in the Ubuntu archives). If it's desired I can attach the whole file. (It isn't actually all that large.)<br>
<br>
" Vim syntax file<br>
" Language: Haskell with literate comments, Bird style,<br>
" TeX style and plain text surrounding<br>
" \begin{code} \end{code} blocks<br>
" Maintainer: Haskell Cafe mailinglist <<a href="mailto:haskell-cafe@haskell.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">haskell-cafe@haskell.org</a>><br>
" Original Author: Arthur van Leeuwen <<a href="mailto:arthurvl@cs.uu.nl" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">arthurvl@cs.uu.nl</a>><br>
" Last Change: 2004 Aug 31<br>
" Version: 1.01<br>
"<br>
" Thanks to Ian Lynagh for thoughtful comments on initial versions and<br>
" for the inspiration for writing this in the first place.<br>
"<br>
" This style guesses as to the type of markup used in a literate haskell<br>
" file and will highlight (La)TeX markup if it finds any<br>
" This behaviour can be overridden, both glabally and locally using<br>
" the lhs_markup variable or b:lhs_markup variable respectively.<br>
"<br>
" lhs_markup must be set to either tex or none to indicate that<br>
" you always want (La)TeX highlighting or no highlighting<br>
" must not be set to let the highlighting be guessed<br>
" b:lhs_markup must be set to eiterh tex or none to indicate that<br>
" you want (La)TeX highlighting or no highlighting for<br>
" this particular buffer<br>
" must not be set to let the highlighting be guessed<br>
"<br>
"<br>
" 2004 February 18: New version, based on Ian Lynagh's TeX guessing<br>
" lhaskell.vim, cweb.vim, tex.vim, sh.vim and fortran.vim<br>
" 2004 February 20: Cleaned up the guessing and overriding a bit<br>
" 2004 February 23: Cleaned up syntax highlighting for \begin{code} and<br>
" \end{code}, added some clarification to the attributions<br>
"<br>
<br>
<table cellpadding="0" cellspacing="0" width="100%">
<tbody><tr>
<td>
-- <br>
<b>Michael T. Richter</b> <<a href="mailto:ttmrichter@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ttmrichter@gmail.com</a>> (<b>GoogleTalk:</b> <a href="mailto:ttmrichter@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
ttmrichter@gmail.com</a>)<br>
<i>It's OK to figure out murder mysteries, but you shouldn't need to figure out code. You should be able to read it. (Steve McConnell)</i>
</td>
</tr>
</tbody></table>
</div>
<br>_______________________________________________<br>Haskell-Cafe mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">
http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br><br><br clear="all"></blockquote></div><br>