From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: yangsx@fltrp.com, caml-list@inria.fr
Subject: Re: [Caml-list] ocaml-mode-3.05
Date: Thu, 8 Aug 2002 08:34:16 +0200 [thread overview]
Message-ID: <20020808063416.GA1033@iliana> (raw)
In-Reply-To: <20020808085059U.garrigue@kurims.kyoto-u.ac.jp>
On Thu, Aug 08, 2002 at 08:50:59AM +0900, Jacques Garrigue wrote:
> From: Yang Shouxun <yangsx@fltrp.com>
> > True. For instance, I'd rather an indentation for every consecutive
> > "let...", as in the Lisp style (I learned Scheme and Common Lisp before
> > Ocaml). That is, I prefer indentation to graphically show the structure
> > of the code, even at the risk of being stretched too much to the right.
> > With higher resolution of graphic displays and more careful organization
> > of the code, I guess the problem may be less imposing.
>
> This is mostly a question of taste: I view most of the let's as
> assignment, so I prefer not to indent them, since they do no more than
> changing a binding. But lots of people would disagree.
>
> By the way, you can customize this in ocaml-mode too:
> (setq caml-let-in-indent 2)
> The default is 0, meaning no indent.
>
> On the other hand, not everything is customizable, and even when
> customizable it may be a pain. For instance, I never came around to
> allow a global change in the size of indentation: this is 2, or you
> have to change it individually for every construct...
>
> > I'm using tuareg for it allows me to run ocaml toplevel in emacs. I'm
> > not sure the ocaml-mode has such functionality.
>
> Let's stop such blaring disinformation:
> running the ocaml toplevel under emacs was the original goal of the caml
> mode, and this already worked more than 10 years ago.
> Thanks to Didier it is now pretty clever about errors, but then Tuareg
> might be just as clever.
Jacques, ...
This is the same caml mode that comes with the ocaml sources, isn't it ?
It is just some changes that you did after the 3.05 release, and which
will go into 3.06, or do you intent to distribute them separatedly ?
Friendly,
Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-08-08 6:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 6:49 Jacques Garrigue
2002-08-06 5:04 ` Blair Zajac
2002-08-06 7:38 ` Jérôme Marant
2002-08-06 9:01 ` Dmitry Bely
2002-08-06 19:23 ` Blair Zajac
2002-08-06 23:37 ` Jeffrey Palmer
2002-08-07 0:18 ` Jacques Garrigue
2002-08-07 5:25 ` Alexander V. Voinov
2002-08-07 5:54 ` Yang Shouxun
2002-08-07 23:50 ` Jacques Garrigue
2002-08-08 1:19 ` Yang Shouxun
2002-08-12 23:11 ` ocaml-info. was: " Alexander V.Voinov
2002-08-12 23:51 ` Henrik Motakef
2002-08-13 9:23 ` Olivier Andrieu
2002-08-13 21:13 ` Alexander V.Voinov
2002-08-08 6:34 ` Sven LUTHER [this message]
2002-08-08 7:12 ` Jacques Garrigue
2002-08-07 6:11 ` Michael Vanier
2002-08-07 6:25 ` Jacques Garrigue
2002-08-07 12:34 ` David Fox
2002-08-07 13:37 ` Jacques Garrigue
2002-08-09 17:16 ` David Fox
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=20020808063416.GA1033@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=yangsx@fltrp.com \
/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