From: "chris.danx" <chris.danx@ntlworld.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Tuareg customisation - doc comments
Date: Fri, 24 Dec 2004 19:15:52 +0000 [thread overview]
Message-ID: <41CC6AE8.9070509@ntlworld.com> (raw)
In-Reply-To: <41C610EB.7070607@1969.ws>
Karl Zilles wrote:
> Kurt Welgehausen wrote:
>
>>> (**
>>> *
>>> *
>>> *)
>>
>>
>>
>> I think you'll find that this breaks ocamldoc, i.e., you'll
>> get '*' embedded in the module description at the top of the
>> main html file.
>
>
> I think if you use the -stars option of ocamldoc, it will work correctly.
Yes indeed. Does anyone know how to configure comments so they're the
same... is this customisable? I scanned through the lisp but am no lisp
expert so if it's not customisable I'll live.
next prev parent reply other threads:[~2004-12-24 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 21:37 chris.danx
2004-12-19 22:59 ` [Caml-list] " Kurt Welgehausen
2004-12-19 23:38 ` Karl Zilles
2004-12-24 19:15 ` chris.danx [this message]
2004-12-29 16:49 ` Albert Cohen
2004-12-29 23:24 ` chris.danx
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=41CC6AE8.9070509@ntlworld.com \
--to=chris.danx@ntlworld.com \
--cc=caml-list@inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).