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

bug: alert user about wrong alex package #776

Closed
AbdealiLoKo opened this issue Sep 2, 2016 · 6 comments
Closed

bug: alert user about wrong alex package #776

AbdealiLoKo opened this issue Sep 2, 2016 · 6 comments
Assignees
Labels

Comments

@AbdealiLoKo
Copy link
Contributor

From @Redridge on February 18, 2016 21:54

Apparently there are 2 alex packages
It would be nice to find a way to alert the user that he has the wrong alex package in his PATH so tests might fail

Copied from original issue: coala/coala#1582

@AbdealiLoKo
Copy link
Contributor Author

From @sils1297 on February 18, 2016 21:56

same is true for the remark package btw. don't know what the other one is. FFor alex it's the lexer for haskel (alex of course)

@AbdealiLoKo
Copy link
Contributor Author

Doesn't the linter give a bunch of warnings as that would give a error in stderr ?
I don't think we should be doing custom checking for package clashes like this ...

@AbdealiLoKo
Copy link
Contributor Author

From @sils1297 on February 19, 2016 9:55

Apparently it just gives no results because the regex doesn't match.

@AbdealiLoKo
Copy link
Contributor Author

I've asked the alex devs if they could make an alias alexjs so that this clash wouldnt be troublesome.
get-alex/alex#83

@AbdealiLoKo
Copy link
Contributor Author

Seems like that's not going to happen.

@gitmate-bot
Copy link
Collaborator

Thanks for reporting this issue! A coalaian will look at it soon.

AbdealiLoKo added a commit that referenced this issue Sep 3, 2016
Alex has a name clash with another tool in the haskell toolkit. Hence,
we check here by reading the `--help` of `alex` and checking whether
this is indeed the correct tool or not.

Fixes #776
AbdealiLoKo added a commit that referenced this issue Sep 3, 2016
Alex has a name clash with another tool in the haskell toolkit. Hence,
we check here by reading the `--help` of `alex` and checking whether
this is indeed the correct tool or not.

Fixes #776
AbdealiLoKo added a commit that referenced this issue Sep 3, 2016
Alex has a name clash with another tool in the haskell toolkit. Hence,
we check here by reading the `--help` of `alex` and checking whether
this is indeed the correct tool or not.

Fixes #776
AbdealiLoKo added a commit that referenced this issue Sep 3, 2016
Alex has a name clash with another tool in the haskell toolkit. Hence,
we check here by reading the `--help` of `alex` and checking whether
this is indeed the correct tool or not.

Fixes #776
AbdealiLoKo added a commit that referenced this issue Sep 3, 2016
Alex has a name clash with another tool in the haskell toolkit. Hence,
we check here by reading the `--help` of `alex` and checking whether
this is indeed the correct tool or not.

Fixes #776
AbdealiLoKo added a commit that referenced this issue Sep 3, 2016
Alex has a name clash with another tool in the haskell toolkit. Hence,
we check here by reading the `--help` of `alex` and checking whether
this is indeed the correct tool or not.

Fixes #776
@AbdealiLoKo AbdealiLoKo self-assigned this Sep 3, 2016
@rultor rultor closed this as completed in fa70e92 Sep 3, 2016
gosom pushed a commit to gosom/coala-bears that referenced this issue Jul 15, 2017
Alex has a name clash with another tool in the haskell toolkit. Hence,
we check here by reading the `--help` of `alex` and checking whether
this is indeed the correct tool or not.

Fixes coala#776
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants