<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>OCaml offers multiple choices for doing things, and I hope that won’t change.</div><div><div>Choosing and advertising for a single editor or editor mode doesn’t sound good to me.</div><div>Therefore, I believe it wouldn’t harm the OCaml community to have some better place and visibility for Tuareg, which could well cohabit with some concurrent projects under the OCaml umbrella. Also I believe <a href="https://github.com/ocaml">https://github.com/ocaml</a> is (at least now) a lot better place than {<a href="http://tuareg.forge.ocamlcore.org">http://tuareg.forge.ocamlcore.org</a> + <a href="https://forge.ocamlcore.org/projects/tuareg/">https://forge.ocamlcore.org/projects/tuareg/</a> which are quite confusing, especially the former which seems even more deprecated than the latter}, especially since a lot of OCaml projects are now under <a href="https://github.com/ocaml/">https://github.com/ocaml/</a>.</div><div><br></div><div>And since the OCaml distribution is being cleaned-up (isn’t it?), perhaps it’s also time to remove the emacs/*.el files from it, and put them somewhere else (perhaps under <a href="https://github.com/ocaml/">https://github.com/ocaml/</a> as well, I don’t really care).</div><div><br></div><div>Yes I’ll be happier if Tuareg moves to <a href="https://github.com/ocaml/tuareg/">https://github.com/ocaml/tuareg/</a>.</div><div><br></div><div><div><div><div>On 05 Jan 2014, at 00:06, Gabriel Scherer <<a href="mailto:gabriel.scherer@gmail.com">gabriel.scherer@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>I hope this does not sound too negative, but I'm not sure we would gain by "blessing" tuareg as "the" ocaml editor mode for Emacs. The parallel existence of caml-mode and tuareg-mode has been a long-time annoyance of mine, because I don't see a strong justification for using either instead of the other. In particular tuareg has had long-standing bugs that are rather annoying, and I for one would be very happy to throw away any kind of elisp-implemented approximation of the OCaml syntax, and use a more principled approach such as Merlin+ocp-index to handle them (none of which currently support syntax highlighting iirc., but that could be added to ocp-index capabilities).<br>
<br></div>I do think however that given the high number of Tuareg users, it is a very good thing that dedicated souls such as Christophe accept the pain of maintaining emacs modes. If he can be pleased by having tuareg repo under's the "ocaml" community umbrella, I see no strong reason why not -- only I won't recommend as strongly all of the software under the "ocaml" umbrella.<br>
<div><div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Jan 4, 2014 at 6:46 PM, Christophe Troestler <span dir="ltr"><<a href="mailto:Christophe.Troestler@umons.ac.be" target="_blank">Christophe.Troestler@umons.ac.be</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Anil,<br>
<div class="im"><br>
On Thu, 2 Jan 2014 14:50:12 +0000, Anil Madhavapeddy wrote:<br>
><br>
> I have no objection. In fact, there are a few other editor tools<br>
> that I'd like to move under the ocaml org in order to "bless" them.<br>
<br>
</div>Since I do not have admin rights on the organization "ocaml", I cannot<br>
transfer the repo. Since there are no issues yet on my version, you<br>
can simply create a tuareg repo and I'll push the current history.<br>
Is it good for you?<br>
<br>
Best,<br>
C.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Infrastructure mailing list<br>
<a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/infrastructure" target="_blank">http://lists.ocaml.org/listinfo/infrastructure</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>Infrastructure mailing list<br><a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a><br>http://lists.ocaml.org/listinfo/infrastructure<br></blockquote></div><br></div></div></div></body></html>