Add error regexps for elixirc and credo #461
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sirikid
force-pushed
the
feature/compilation-error-regexp-alist-alist
branch
4 times, most recently
from
86f9762 to
4c6b29f
Compare
sirikid
force-pushed
the
feature/compilation-error-regexp-alist-alist
branch
from
4c6b29f to
32c5731
Compare
sirikid
force-pushed
the
feature/compilation-error-regexp-alist-alist
branch
from
32c5731 to
cb247d2
Compare
|
|
@Trevoke any ideas on this? The regexps look sane to me (and well documented!), but I'm not familiar with emacs regexps. |
|
I am continuing to work on this here. |
|
All regexps are written using real build logs and re-builder. |
J3RN
pushed a commit
to J3RN/emacs-elixir
that referenced
this pull request
Apr 24, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.