3It can be tempting to keep all GHC extensions in your stack.yaml or cabal file but many haskell tools don't have integrations with build tools like stack and cabal, and thus would break if they don't see an explicit language pragma at the start of the file.
5Hext alows you to mainain a single list of GHC extensions and automatically apply them to every file.
7Create a `.hext.yaml` file and put it into your project directory:
28You can create multiple groups with different GHC extensions.
30`line_limit` can be abset, indicating that every extensions should be on its own line, a positive int or `none`, indicating that all extensions should be placed on one lines.
keysesc to close
- j k
- move down, up
- enter
- open
- esc
- back, or up a level
- 1 2 3 4
- readme, files, commits, refs
- /
- filter
- y
- copy the clone command
- c
- compare the chosen commit with another (or shift-click both)
- ?
- show or hide this list