Yes, perhaps just agreeing on sane defaults is a more achievable goal. Cursive currently does not indent everything exactly according to the guide by default. I would also not like to see tools' ability to implement more sophisticated formatting hampered by an overly restrictive guide either, since a lot of users have requested that Cursive do different things with particular forms, but having agreed defaults doesn't conflict with this.
On 20 December 2014 at 22:51, Laurent PETIT <laurent.pe...@gmail.com> wrote: > I agree that if all tools could agree on sale out of the box defaults, > this would be very valuable to users and clojure in general. > > Maybe a less ambitious goal than getting the whole community agree on > standards could be tool authors to agree on shared defaults. Which of > course doesn't prevent the tools to offer additional options, but > activating those would require users to explicitly customize the tools > settings. > > Le samedi 20 décembre 2014, Lars Andersen <ex...@expez.com> a écrit : > > My view on this is very much along the line of discussions about >> whitespace. While I have opinions about these matters, for the most part I >> don't want to think about it--I have more pressing concerns. What's >> important to me is consistency within a code base. Just like with >> whitespace, I don't want to introduce spurious changes into all my diffs >> when working with other people. I also don't want to customize 50 editor >> variables to get sane defaults which I have to tweak for various >> environments (work, home, contributing to open source projects). >> >> Supporting different styles is a laudable goal, but I hope we can agree >> that the defaults should be similar in all editors to reduce friction when >> working with others. Using a style guide maintained by the community for >> those defaults make a lot of sense to me. >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Laurent Petit > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
