-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Fix stack trace #4428
Merged
GeoffreyBooth
merged 14 commits into
jashkenas:master
from
GeoffreyBooth:fix-stack-trace
Jan 22, 2017
Merged
Fix stack trace #4428
Changes from 7 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
0b0323b
Revert aee27fbff03870c5479c6c33e6b1f1a32219420c
GeoffreyBooth c70541b
Patch Jison’s output so that it requires `fs` only if we’re truly in …
GeoffreyBooth e2ac4b9
Temporary fix for exceptions getting thrown when trying to generate a…
GeoffreyBooth 96a8776
Save the test REPL history in the system temp folder, not in the Coff…
GeoffreyBooth 86e7d56
Rewrite `getSourceMap` to never read a file from disk, and therefore …
GeoffreyBooth c83410b
Add test to verify that stack traces reference the correct line numbe…
GeoffreyBooth 51097cd
Get the parser working in the browser compiler again; rather than det…
GeoffreyBooth 316a9f3
Follow Node’s standard of 4-space indentation of stack trace data
GeoffreyBooth e117647
Merge branch 'master' of github.com:jashkenas/coffeescript into fix-s…
GeoffreyBooth 14876e4
Better .gitignore
GeoffreyBooth 23e9fc7
Fix caching of compiled code and source maps; add more tests to verif…
GeoffreyBooth 6f03c8a
Better fallback value for the parser source
GeoffreyBooth 27c2833
Fix the stack traces and tests when running in a browser
GeoffreyBooth f6a2384
Update the browser compiler so that @murrayju doesn’t have any extra …
GeoffreyBooth File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While were improving all of this anyway, I think we should take the opportunity to indent the "at" lines just like Node.js does. That is, 4 spaces instead of 2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh, really? I hate 4-space indentation . . .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also prefer 2-space indentation in general, but I thought it might be a good idea to match the standard error formatting as closely as possible?