Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Initializing a project with a literate Main file does not compile #5577

Closed
emanuelbuholzer opened this issue Sep 17, 2018 · 0 comments
Closed

Initializing a project with a literate Main file does not compile #5577

emanuelbuholzer opened this issue Sep 17, 2018 · 0 comments

Comments

@emanuelbuholzer
Copy link

emanuelbuholzer commented Sep 17, 2018 •
edited
Loading

Initializing a project with a literate Main file does not compile. Cabal writes the same content for both a Main.hs and a Main.lhs file. Could we extend cabal such that it generates a valid Main.lhs file?

e.g.

> module Main where

> main :: IO ()
> main = putStrLn "Hello, Haskell!"
hrhino added a commit to hrhino/cabal that referenced this issue Dec 20, 2018
@hrhino
Prepend "> " to lines of generated Main.lhs
df0777c 
This makes it valid Literate Haskell.

Fixes haskell#5577.
hrhino added a commit to hrhino/cabal that referenced this issue Dec 20, 2018
@hrhino
Generate valid Main.lhs files with cabal init.
3d949a7 
Fixes haskell#5577.
@hrhino hrhino mentioned this issue Dec 20, 2018
Merged
4 tasks
23Skidoo pushed a commit to hrhino/cabal that referenced this issue Jan 15, 2019
@hrhino @23Skidoo
Generate valid Main.lhs files with cabal init.
22ebfeb 
Fixes haskell#5577.
23Skidoo pushed a commit to hrhino/cabal that referenced this issue Jan 21, 2019
@hrhino @23Skidoo
Generate valid Main.lhs files with cabal init.
97f3213 
Fixes haskell#5577.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@emanuelbuholzer