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 have had issues with hasktags and emacs when involving literate files in Bird notation
E-macs version: 26.1
Consider a file like this:
This is foo:
> dataFoo=Bar
> a::Foo> a =Bar
When jumping to the definition of Foo, emacs will complain that it cannot find the line "^ data Foo". I assume this is because the TAGS file generated by hasktags --etags does not account for the leading > .
I would prefer hasktags to directly say that Bird notation is not supported, and perhaps even point me to some way to convert to \begin{code}\end{code} notation:
I have had issues with
hasktags
and emacs when involving literate files in Bird notationE-macs version: 26.1
Consider a file like this:
When jumping to the definition of
Foo
, emacs will complain that it cannot find the line "^ data Foo". I assume this is because theTAGS
file generated byhasktags --etags
does not account for the leading>
.I would prefer
hasktags
to directly say that Bird notation is not supported, and perhaps even point me to some way to convert to\begin{code}
\end{code}
notation:https://wiki.haskell.org/Literate_programming#Transformation_of_.lhs-files
I could provide more detail steps on how to reproduce the bug, but it seems that the trend is to drop support for Bird notation altogether.
The text was updated successfully, but these errors were encountered: