New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ocaml.vim script not working correctly #8446
Comments
Comment author: administrator [Holger, I am forwarding your mail to Markus, the author of ocaml.vim]
|
Comment author: administrator This is not a bug in OCaml proper. Forwarded to Markus. -DD 2004-01-14 |
Comment author: administrator Hi Damien and Holger, I have tried the code below with Vim-version 6.2.149, and it doesn't You may have to set the variable "iskeyword" to include the underscore Regards, -- On Wed, 14 Jan 2004, Damien Doligez wrote:
|
Comment author: administrator Hi Markus, Sorry, my mistake. I tried a normal .ml-file and got no error. thank you and sorry, holger On Thu, 15 Jan 2004, Markus Mottl wrote:
|
Original bug ID: 2036
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Holger Dell
Version: OCaml-3.07p2
OS: Windows/Cygwin (sorry)
Submission from: p508ae11c.dip.t-dialin.net (80.138.225.28)
Hi,
I am using Vim 6.2 and got a problem with the file
http://www.ai.univie.ac.at/~markus/ocaml_sources/ocaml.vim
(link can be found at http://www.ocaml.org).
the syntax highlighting doesn't work correctly.
if you have the following code:
let xs = [1; 2; 3] in
let f x = false in
let x = List.for_all f xs
and b = "foo"
the syntax-highlighting thinks "for" is the beginning of a "for"-loop, so the
syntax highlighting after that point doesn't work correctly.
and i think that's because the vim-script treats "_" like a whitespace, and that
is obviously incorrect.
the problem is not only with "for", it also happens with "begin" or "open" as
well.
it's not a serios bug, but it is annoying, please fix that.
thank you.
The text was updated successfully, but these errors were encountered: