<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>If erlfmt gave me a single, consistent, format to un-format to my
liking, for my own private viewing, it would be good enough for
me.</p>
<p>These, purely private, sources would be erlfmt'ed before I
release them to other viewers.<br>
</p>
<p>gofmt is not configurable. On purpose.<br>
</p>
<br>
<div class="moz-cite-prefix">On 08/30/2016 09:54 AM, Vlad Dumitrescu
wrote:<br>
</div>
<blockquote
cite="mid:CAA-EFXvjfmmgob36XEeeuHX+8b1pehrNXoXUWh_iZuaAKN3C0g@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">Hi,
<div><br>
</div>
<div>Sourcer would have some advantages, yes, but it's still in
very early stages. The goal is to have an AST as compatible as
possible with the standard one, so for the time being it is
less important which parser is used. For formatting
syntactical correct files there should be no difference.</div>
<div><br>
</div>
<div>My take on this is that the first step is to define what
the right way to format code is, in form of a specification or
a test suite to be passed by the formatter. A big part of this
is to decide if formatting should be "indentation only" or
"full rewrite" or both - there are arguments to be made for
each variant. Another one is about how to indent (tabs,
spaces, how many) and how wide the page is (80 characters may
feel too narrow for today's monitors, but sometimes code has
to be read/edited on narrow terminals). Different use cases
need different configuration, I'm not sure if it's possible to
have one solution to please everybody. </div>
<div><br>
</div>
<div>best regards,</div>
<div>Vlad</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Aug 29, 2016 at 11:41 PM,
Tuncer Ayaz <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:tuncer.ayaz@gmail.com" target="_blank">tuncer.ayaz@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for
sharing the project. My thoughts follow.<br>
<br>
vim-erlang-runtime[0] output is very close to erlang.el, and
it<br>
doesn't suffer from some of the parsing erros of current
erlang.el (as<br>
reported on <a moz-do-not-send="true"
href="http://bugs.erlang.org" rel="noreferrer"
target="_blank">bugs.erlang.org</a>). vim might be more
readily available in<br>
your CI env, if you want to automatically check for style
regressions.<br>
<br>
Also, Bengt's bepp[1][2] looks useful.<br>
<br>
However, I think Vlad's sourcer might be the best base for
an escript<br>
and plugin, especially because it aims to be forgiving with,
say,<br>
unfinished code. This is very important for use in editors.<br>
<br>
[0] <a moz-do-not-send="true"
href="https://github.com/vim-erlang/vim-erlang-runtime"
rel="noreferrer" target="_blank">https://github.com/vim-erlang/<wbr>vim-erlang-runtime</a><br>
<br>
[1] <a moz-do-not-send="true"
href="https://github.com/ebengt/erlang_stdin_formatter"
rel="noreferrer" target="_blank">https://github.com/ebengt/<wbr>erlang_stdin_formatter</a><br>
[2] <a moz-do-not-send="true"
href="https://github.com/ebengt/erlang_string_io"
rel="noreferrer" target="_blank">https://github.com/ebengt/<wbr>erlang_string_io</a><br>
<br>
[3] <a moz-do-not-send="true"
href="https://github.com/erlang/sourcer" rel="noreferrer"
target="_blank">https://github.com/erlang/<wbr>sourcer</a><br>
<div class="HOEnZb">
<div class="h5">______________________________<wbr>_________________<br>
erlang-questions mailing list<br>
<a moz-do-not-send="true"
href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a moz-do-not-send="true"
href="http://erlang.org/mailman/listinfo/erlang-questions"
rel="noreferrer" target="_blank">http://erlang.org/mailman/<wbr>listinfo/erlang-questions</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>