To back him up, it seems that the lhaskell.vim syntax highlighter is broken with Vim 7.1. Here, it is definitely using lhaskell.vim, but doesn't seem to be parsing the code in between \begin{code} and \end{code} as Haskell. I can't work out why though, it seems that the addition of \@= to the end pattern of the code region is causing it to not be recognised, but removing it causes other problems. Adding the keepend option makes it work nicely for the first block, but fail to highlight later blocks. On 05/06/07, Ilya Tsindlekht wrote:

On Tue, Jun 05, 2007 at 04:58:40PM +0800, Michael T. Richter wrote:

...

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.

I still get a dog's breakfast.

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 http://img357.imageshack.us/img357/5798/gvimexamplezv4.png. (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 some 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).

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.) It seems to me like VIM thinks your file is a (La)TeX file. Can you check that your filetype variable is set to lhaskell? (Type :set filetype) It should be if your file has extension .lhs. If it isn't, try setting it manually (:set filetype=lhaskell)

---

Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

On Tue, 2007-05-06 at 12:30 +0300, Ilya Tsindlekht wrote:

It seems to me like VIM thinks your file is a (La)TeX file. Can you check that your filetype variable is set to lhaskell? (Type :set filetype) It should be if your file has extension .lhs. If it isn't, try setting it manually (:set filetype=lhaskell)

Damn! I deleted the wrong image when I set that up. The original image I was going to use had a thing at the bottom with all of :set's changed variables displayed. Filetype was definitely set to lhaskell. -- Michael T. Richter (GoogleTalk: ttmrichter@gmail.com) The most exciting phrase to hear in science - the one that heralds new discoveries - is not "Eureka!" but "That's funny..." (Isaac Asimov)

the following sequence seems to help (tested on ghc/compiler/stranal/StrictAnal.lhs): :syn sync fromstart :syn region texZone matchgroup=hsLineComment start="\\begin{code}" end="\\end{code}" contains=@haskellTop keepend matchgroup=NONE i'll leave it to those who are actually using literate haskell to check this and to have it included in lhaskell.vim if it is helpful. claus ----- Original Message ----- From: "Claus Reinke" To: Sent: Tuesday, June 05, 2007 1:28 PM Subject: literate haskell syntax highlighting issues in vim (Re:[Haskell-cafe] OK,so this VIM thing -- how do I make it actually work?)

...

...

clearly.) The problems I'm seeing are the ugly white-on-red for underlines, the lack of any kind of differentiation for You can also put your cursor an those underlines and use

:echo synIDattr(synID(line("."), col("."), 1), "name")

looks like a highlighting bug alright. reduced example:

------------------------ H.lhs:

% \section{one}

\begin{code} data D_e = D String deriving Show \end{code}

% \section{two}

data D_e = D String deriving Show

------------------------

as it is, the first code line is haskell-highlighted, the "_" is part of a "ConId"; the second code line is tex-highlighted, the "_" becomes a "texOnlyMath", and is highlighted as a syntax error (red).

if i uncomment the "\section{one}", haskell-highlighting disappears, everything is now part of a "texSectionZone", and highlighted as such, including tex syntax error highlights. if i now register code-sections as "texZone" (the zone "tex.vim" uses for "verbatim"), with haskell contents, both code lines are haskell-highlighted, so the "texSectionZone" has been interrupted..

:syn region texZone start="\\begin{code}" end="\\end{code}" contains=@haskellTop

if i now uncomment the "\section{two}", a new "texSectionZone" is started there (might need a resync), and both code lines are highlighted correctly (the first as haskell, the second as -buggy- tex).

"tex.vim" has several zones with no real end marker ("\section", "\chapter", ..), and it seems that "tex.vim" and "lhaskell.vim" do not interact properly. since this list is given as the maintainer for "lhaskell.vim": any literate haskellers out here who'd like to try fixing that?-)

claus

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

[mailto:haskell-cafe-bounces@haskell.org] On Behalf Of Dougal Stanton

On 05/06/07, Claus Reinke wrote:

...

(tested on ghc/compiler/stranal/StrictAnal.lhs):

Since when did GHC become NSFW?! :-O

/ducking and running...

Says more about you than anything else... ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************

On Tue, 2007-05-06 at 13:05 +0200, Georg Neis wrote:

"Michael T. Richter" wrote:

...

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 some 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).

Same here. I've just played around and found that the following helps: :let b:lhs_markup="none" :e

That did it, Georg. Thanks. Now to figure out how to make that happen all the time (and how to make vim automatically do syntax highlighting instead of having to manually turn it on each time I run it), then I'm back on track to regressing about 20 years of editor use. :( -- Michael T. Richter (GoogleTalk: ttmrichter@gmail.com) Never, ever, ever let systems-level engineers do human interaction design unless they have displayed a proven secondary talent in that area. Their opinion of what represents good human-computer interaction tends to be a bit off-track. (Bruce Tognazzini)

Michael, Michael T. Richter wrote:

So, I guess I'm back to my original question: where can I find a decent editor that can do syntax highlighting out of the box for literate Haskell? (Or, alternatively, where can I find a syntax-highlighting editor I can expand the syntax handling of on my own?) VIM is broken out of the box and if I'm going to mess around with syntax highlighting files, I'd at least like to do it in an editor I'm likely to be comfortable in.

I can't recall whether you were asking about linux or running on Windows under cygwin. On linux (fedora-5 + gnome) I've settled on using the "kate" editor within a gnome/fedora-5 setup. It provides syntax highlighting that seems to work fine with .hs and .lhs files. If I remember, this worked "out of the box" (installed via yum). There is a link to its home page (http://kate-editor.org/kate) from the Haskell wiki. Just a suggestion ... as with all editors, it probably has some features you like, some you loathe ..! David. -- Dr. David Duke Email: djd@comp.leeds.ac.uk School of Computing Web: www.comp.leeds.ac.uk/djd/ University of Leeds Tel: +44 113 343 6800 Leeds, LS2 9JT, U.K. Fax: +44 113 343 5468

Perhaps you could just highlight the small subset of LaTeX that is common in .lhs files? This seems like it would be satisfactory in most cases. On 05/06/07, Paul Moore wrote:

On 05/06/07, Michael T. Richter wrote:

...

Oops. I spoke too soon. It works ... for about a third of the file. It then loses its mind in the middle of a do-block (in a sizable chunk of code) and doesn't regain it until the next code begin/end pairing ends.

There is a fix for this (:syn sync fromstart is the usual incantation that helps) but (as a Vim user) I take your point that Vim's highlighting is not as you want it out of the box, and that matters.

So, I guess I'm back to my original question: where can I find a decent

...

editor that can do syntax highlighting out of the box for literate Haskell? (Or, alternatively, where can I find a syntax-highlighting editor I can expand the syntax handling of on my own?) VIM is broken out of the box and if I'm going to mess around with syntax highlighting files, I'd at least like to do it in an editor I'm likely to be comfortable in.

You need to take into account the fact that highlighting literate Haskell is hard, if you want it done completely right, because there are two entirely distinct sets of syntax (Haskell and LaTeX) being interspersed (and from the look of one of your examples, you use CPP syntax in places as well). That is never going to be easy to handle. If you were happy with the LaTeX being left unhighlighted, it wouldn't be too hard to handle. Equally, if you want the LaTeX highlighting with the Haskell unhighlighted, that's easy enough as well. It's the combination that's hard.

So, you should probably:

1. Accept that you're going to have very few, if any, good options 2. Think about your priorities - if you have to give something up, what would hurt you least? (FWIW, if you're happy for the LaTeX to be left unhighlighted, setting lhs_markup="none" in Vim might be enough for you).

Beyond that, I can't offer any suggestions - I use Vim and am happy with it, but I know it's limited when dealing with mixed-type files (HTML + CSS + JavaScript is another common case).

Hope this helps, Paul.

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe