While I agree the original reasons for 80 char limit is rather antiquated, there are still valid reasons today. I tend to keep the 80 chars limit, simply because it allows me to open two files side-by-side without wrapping. That said, I'm don't feel extremely strong about this and even break that rule often myself.
Michał. > On 30 Oct 2016, at 11:40, José Valim <[email protected]> wrote: > > The omission is somewhat intentional as nobody had a strong use case for it. > Specially given not using fenced blocks is more readable for those reading > the documentation inline. > > Also, can I take the opportunity to do a small rant on the 80 spaces limit? > It is quite antiquated as a default. Sure, if you prefer it, then fine, but I > would not pick it as a default value. IIRC is a limit that comes from punch > cards. > > Some still defend it based on typograph but those usually recommend 66CPL as > best and a maximum of 75. On the other hand, there is a study (a bit old at > this point) that measured faster reading times for eletronic mediums with > 95CPL: > https://www.researchgate.net/publication/253615156_The_Effects_of_Line_Length_on_Reading_Online_News > > The paper also shows a strong preference for 35CPL! > > If someone is aware of more recent studies or studies specific for > programming purposes, please let me know. > > I personally prefer 95/100, as Elixir leads to horizontal code with pattern > matching, well-named variables, multiple arguments, etc. But it is a personal > preference. I wouldn't dare to argue it is an ideal value. :) > > On Sunday, October 30, 2016, Chris Keele <[email protected]> wrote: > Hey all, > > I'm trying to get a project into 80 character lines. Most of the credo > violations are long ExUnit doctest lines. > > I notice that IO.Ansi.Docs and ExDoc both have support for fenced code > blocks, which I prefer in Markdown and would dedent my problem lines > sufficiently. However, when I try to run doctests with them, I get: > > Doctest did not compile, got: (SyntaxError) lib/library.ex:14: unexpected > token: "`" (column 1, codepoint U+0060) > code: 4 > ``` > stacktrace: > lib/library.ex:13: Library (module) > > Is this omission intentional, or a feature request I could hack on? > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/9560079b-c0e6-4007-9d10-3850a9aa6316%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > > -- > > > José Valim > www.plataformatec.com.br > Skype: jv.ptec > Founder and Director of R&D > > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2B4pMH25DMr_tKL0_SrFGVjnuhP%3DoBe-3Tf7pY4%3DvMFvA%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/0932CE73-390D-4675-B9C0-F388C60B3BD4%40muskala.eu. For more options, visit https://groups.google.com/d/optout.
