-
Notifications
You must be signed in to change notification settings - Fork 6
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
Link through to files from stack trace #14
Comments
Ahh, yes, very helpful! more and more like a proper compilation buffer after all! :) Perhaps it's time to stop using Thinking out loud, huh, maybe we can just put the buffer in a bit unrelated, wanna be a contributor or whatever github calls it - get a commit bit for this repo ? you've been gracious enough to refactor & improve more than half the code :P and uhhh i dunno, maybe it'd be easier not to work with forks and stuff. :) |
Yeah! That would be sweet! But I'd still probably open PRs for visibility :P But yeah, I tried to convert it from an I think both sentinels and filters would both work? I may be missing the subtleties between them, but isn't it just the sentinels run on a status update (i.e. exit code) and filters run on text before it's passed through to the buffer? I had a bit of a play last night and got it working with a sentinel, and seeing as the output buffer's read only, I couldn't really interact with it until it had finished anyway :) What free stuff does |
yeah PRs are definitely the way to go :D. branches for days! :) I believe I've granted push permissions - you probably already know, but melpa unstable builds directly off of the master branch, and melpa stable builds off of tags. yep i just learned about sentinels earlier this week fooling around with trying to get i presumed one of those modes would get include g to rerun and automatically buttonify file references, at least. but, i didn't actually check. :P |
if it's of assistance, seems to be how karma.el does it: https://github.com/tonini/karma.el/blob/master/karma.el#L172 although, seems like it'll be pretty specific to the error message to do it this way. for example, error messages with source maps probably want to go to the source instead of the transpiled code. hum. |
FWIW, I opened #31. |
I've pulled master, I can see compilation mode being applied to the buffer but none of the error regexps seem to be being applied. Have either of you got this working? Is there a regexp I should be adding to |
It works for me with eslint & grunt, using the UNIX formatter of eslint. |
When grunt tasks error (mainly thinking about jasmine tests etc) and a stack trace is printed out, e.g.
It would be nice to be able to click through to
testSpec.js:125
from(†)
.I've been playing around with this idea on my branch, button-links. It's currently functional but haven't driven it out with tests, also, the links (emacs
buttons
) are only made whengrunt--highlight-process-links
is called, which has to be done manually or by navigating usingC-c C-n
orC-c C-p
.The text was updated successfully, but these errors were encountered: