+1 for stylish-haskell --- I have it enabled in my save-hook for most of my patches. It would be good to check in a stylish haskell YAML dotfile into the repo with some sane/uncontroversial settings (I like the horizontal alignment but a lot of people don't), then make a one-time pass over the repo. It will cause merge conflicts on any pending merge request however. On Tue, Mar 19, 2013 at 3:23 PM, Brent Yorgey <byorgey@seas.upenn.edu>wrote:
On Mon, Mar 18, 2013 at 06:08:35PM -0700, Jason Dagit wrote:
On Mon, Mar 18, 2013 at 5:15 PM, Ben Millwood <haskell@benmachine.co.uk wrote:
Hi everyone,
Do we have a general notion of what we consider best practices for contributed code to Cabal? Perhaps we should formalise something?
One of the reasons I wanted to get the wiki back online was in the hope that it had some pointers, but it doesn't seem to. (I've started migrating stuff anyway: have a look at https://github.com/haskell/** cabal/wiki/Migration-from-trac< https://github.com/haskell/cabal/wiki/Migration-from-trac>for status).
For example, many of the Cabal modules have explicit, and therefore quite long, import lists, with no clear organisation, and hence when adding new imports I have to read the entire list to make sure they are not already there, and then wonder where makes sense to insert them. Usually I just make something up with no pattern to it, and hence perpetuate the problem.
My experience is that without an automated tool or editor command to organize the headers humans are unlikely to do it. A quick google search didn't turn up any vim or emacs commands for this relating to haskell.
We have
http://hackage.haskell.org/package/stylish%2Dhaskell
which is integrated into Chris Done's extensions to the emacs haskell-mode: https://github.com/haskell/haskell-mode.
-Brent
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://www.haskell.org/mailman/listinfo/cabal-devel
-- Gregory Collins <greg@gregorycollins.net>