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.

Sign up for GitHub

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

Jump to bottom

Backtrace Information #78

Closed
ChrisRackauckas opened this issue Jun 1, 2016 · 1 comment
Closed

Backtrace Information #78

ChrisRackauckas opened this issue Jun 1, 2016 · 1 comment
Labels
Status: Available Type: Enhancement

Comments

@ChrisRackauckas
Copy link
Contributor

Currently the backtrace information does not tell you where the error occurred. It should tell the file and the line in order to be useful.

error
@MichaelHatherly
Copy link
Member

Better info here would indeed be good. The markdown parser doesn't track line/column info currently though, so would probably need us to search through the original file contents in Documenter itself.

@MichaelHatherly MichaelHatherly mentioned this issue Aug 31, 2016
Closed
@mortenpi mortenpi mentioned this issue Oct 31, 2018
Closed
@mortenpi mortenpi mentioned this issue Jan 24, 2019
Merged
fredrikekre added a commit that referenced this issue Jan 24, 2019
@fredrikekre
Better log messages for failed at-meta, at-docs,
98cdf69 
at-autodocs, at-eval, at-example and at-setup blocks,
fix #78.
fredrikekre added a commit that referenced this issue Jan 24, 2019
@fredrikekre
Better log messages for failed at-meta, at-docs,
9c62788 
at-autodocs, at-eval, at-example and at-setup blocks,
fixes #78 and fixes #248.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Available Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ChrisRackauckas @MichaelHatherly