From: Simon Cruanes <simon.cruanes.2007@m4x.org>
To: Drup <drupyog+caml@zoho.com>
Cc: Christophe Troestler <Christophe.Troestler@umons.ac.be>,
OCaml Mailing List <caml-list@inria.fr>,
Sebastien.Hinderer@inria.fr
Subject: Re: [Caml-list] Coding style: mixing tabs and spaces in indentation
Date: Tue, 5 Jan 2016 16:42:27 +0100 [thread overview]
Message-ID: <20160105154227.GP8217@nunchakus.loria.fr> (raw)
In-Reply-To: <568BE2EB.4030203@zoho.com>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
Anecdotally, this was recently on hacker news:
http://ukupat.github.io/tabs-or-spaces/
the OCaml part shows that most OCaml repos on github use 2 spaces, some
use 4 spaces, and very few use tabs.
Le Tue, 05 Jan 2016, Drup a écrit :
> Well, there is an implicit consensus, it's called ocp-indent ....
>
> Le 05/01/2016 14:46, Christophe Troestler a écrit :
> >On Tue, 5 Jan 2016 10:12:24 +0100, Sébastien Hinderer wrote:
> >>Dear all,
> >>
> >>I am wondering whether there are some guidelines that have been proposed
> >>regarding the way OCaml code should be presented?
> >>
> >>More specifically: am I correct that it is considered not such a good
> >>practise to mix tabs and spaces in code indentation? And if so, are
> >>there objective reasons for that?
> >>
> >>It seems Emacs is configured to do that (mixing tabs and spaces) by
> >>default, can anybody confirm?
> >Indeed. You have to put
> >
> > (setq-default indent-tabs-mode nil)
> >
> >in your ~/.emacs.d/init.el file.
> >
> >Best,
> >C.
> >
> >
> >P.S. If there is a consensus on this list that TABs shouldn't be used for OCaml code, I can enable this for OCaml files in Tuareg.
> >
>
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
--
Simon Cruanes
http://weusepgp.info/
key 49AA62B6, fingerprint 949F EB87 8F06 59C6 D7D3 7D8D 4AC0 1D08 49AA 62B6
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-05 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 9:12 Sébastien Hinderer
2016-01-05 9:18 ` Francois Berenger
2016-01-05 9:34 ` David MENTRE
2016-01-05 9:55 ` Raphaël Proust
2016-01-05 13:46 ` Christophe Troestler
2016-01-05 15:36 ` Drup
2016-01-05 15:42 ` Simon Cruanes [this message]
2016-01-05 21:25 ` Hendrik Boom
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=20160105154227.GP8217@nunchakus.loria.fr \
--to=simon.cruanes.2007@m4x.org \
--cc=Christophe.Troestler@umons.ac.be \
--cc=Sebastien.Hinderer@inria.fr \
--cc=caml-list@inria.fr \
--cc=drupyog+caml@zoho.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;
as well as URLs for NNTP newsgroup(s).