You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been through the language addition guide, and would like some advice on implementing support for literate files (e.g. literate haskell, *.lhs).
In a literate file, the code is demarcated, whereas the comments are not. Traditionally literate haskell files used bird tracks.
This is a text description, that is stripped by the _literate preprocessor_.
> -- This is a normal comment> example :: IO ()> example = print "This is code"
More common now is the markdown style.
This is a text description, that is stripped by the _literate preprocessor_.
```haskell-- This is a normal commentexample::IO()
example =print"This is code"```
In either case, rather than demarcating the comments, it is the code which is demarcated, and therefore it does not appear that tokei can simply support such a file by extending the languages.json file.
How can tokei support such a syntax?
The text was updated successfully, but these errors were encountered:
@dbaynard Hello and thank you for this issue. This will require being added as a code path I think tokei can maybe support this syntax though I have a couple of questions about literate files. How many other types of styles are common? Can a *.lhs file have non haskell code fences and still be valid to the compiler?
Hello,
I've been through the language addition guide, and would like some advice on implementing support for literate files (e.g. literate haskell,
*.lhs
).In a literate file, the code is demarcated, whereas the comments are not. Traditionally literate haskell files used bird tracks.
More common now is the markdown style.
In either case, rather than demarcating the comments, it is the code which is demarcated, and therefore it does not appear that tokei can simply support such a file by extending the
languages.json
file.How can tokei support such a syntax?
The text was updated successfully, but these errors were encountered: