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.

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

at pattern of compilation error regexp alist wrong in ghcid.el #1744

Open
codygman opened this issue Apr 19, 2021 · 4 comments
Open

at pattern of compilation error regexp alist wrong in ghcid.el #1744

codygman opened this issue Apr 19, 2021 · 4 comments

Comments

@codygman
Copy link
Contributor

I think it might be wrong in general, but I don't know all the places people use this from which could have a different format.

The problem is that bound at in bound at /home/cody/file/path/here.hs:40:1 is part of the match. When I do M-x next-error and it lands on that filepath it breaks the other links too somehow.

I'm using:

haskell-mode-20210407.214
Emacs 28.0.50
@purcell
Copy link
Member

purcell commented Apr 22, 2021

The issue title mentions ghcid.el - is this really a haskell-mode issue?

@codygman
Copy link
Contributor Author

Maybe. The pattern added by haskell-mode in haskell-compile.el isn't matched right in ghcid.el. If that breaks ghcid.el but not haskell-compile I guess it's a ghcid.el issue. I'm not yet sure if it breaks haskell-compile.el.

I just tried using haskell-compile and it seems to be more broken in that none of the errors get highlighted. Also without ghci open the compilation output opens in fundamental mode.

@purcell
Copy link
Member

purcell commented Apr 25, 2021

I just tried using haskell-compile and it seems to be more broken in that none of the errors get highlighted.

If you provide some steps to reproduce, with corresponding haskell code, versions etc., then I might be able to take a look.

Also without ghci open the compilation output opens in fundamental mode.

I didn't understand this one, sorry.

@codygman
Copy link
Contributor Author

I'll try to write up repro steps sometime today, but this morning I saw stack updated something related to emacs/vim quickfix that didn't add extra indentation.

I use stack, so that could be the difference here:

commercialhaskell/stack#5523

It could be that Cabal alone works fine with this pattern regex.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants