Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Edgar Friendly <thelema314@gmail.com>
To: Richard Jones <rich@annexia.org>
Cc: caml-list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] GtkSourceView2.0 syntax highlighting
Date: Tue, 29 May 2007 16:31:32 -0500	[thread overview]
Message-ID: <465C9BB4.2020301@gmail.com> (raw)
In-Reply-To: <20070529194759.GA4398@furbychan.cocan.org>

Richard Jones wrote:
> On Tue, May 29, 2007 at 02:04:52PM -0500, Edgar Friendly wrote:
>> * Comments (* *), and within them, email addresses, net addresses and
>> TODO/FIXME/XXX
> 
> Are (** ... *) (ocamldoc) comments shown differently?  If that's easy
> to do, it might be worthwhile.
> 
Yes, it's easy.

Inside ocamldoc comments, there's various @-tags.  Are there any that
should have special handling (specially formatting what follows them?),
or just highlight them, or highlight the lines they're in?

There also seem to be stop comments.  I might as well highlight those,
but I don't think it's possible (or if possible, worth the complexity)
to try enabling and disabling ocamldoc highlighting in the right places
so that comments that won't appear in the documentation get a different
highlighting.  If someone is really interested, they're more than
welcome to give it a try.

>> * List literals - [ elem1; elem2; elem3 ]
>>
>> * Array literals - [| elem1; elem2; elem3 |]
> 
> These would be nice, if possible.
>
How do you want the contents to look, same as they would outside the
literal, or the same style throughout (like strings)?

E.


  reply	other threads:[~2007-05-29 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 19:04 Edgar Friendly
2007-05-29 19:47 ` [Caml-list] " Richard Jones
2007-05-29 21:31   ` Edgar Friendly [this message]
2007-05-29 21:36 ` Robert Roessler
2007-05-30  5:30   ` Edgar Friendly
2007-05-30  1:02 ` skaller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=465C9BB4.2020301@gmail.com \
    --to=thelema314@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=rich@annexia.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox