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

Better location format for reporting errors in ocamldoc #4518

Closed
vicuna opened this issue Mar 6, 2008 · 4 comments

Comments

Projects
None yet
2 participants
@vicuna
Copy link

commented Mar 6, 2008

Original bug ID: 4518
Reporter: @dbuenzli
Status: acknowledged (set by @damiendoligez on 2008-03-07T12:36:25Z)
Resolution: open
Priority: normal
Severity: feature
Category: ocamldoc
Tags: junior_job
Related to: #6069

Bug description

Related to #4515 the format used by ocamldoc to report errors does not allow to use emacs' next error to directly jump at the location. E.g. :

/Users/dbuenzli/devel/xmlm/src/xmlm.mli : Syntax error in text:
Same as {!input_tree} but reads a complete {{:#TYPEsignal}valid}
sequence of signals.

{b Raises {!Error} on input errors.

line 3, character 39:
{b Raises {!Error} on input errors.

should be something like :

File "src/xmlm.mli", line 3, character 39:
...

Thanks,

Daniel

@vicuna

This comment has been minimized.

Copy link
Author

commented Dec 23, 2013

Comment author: lebedev

I've started working and this and I'm not sure if warnings should have the same location information header? Any suggestions?

@vicuna

This comment has been minimized.

Copy link
Author

commented Sep 12, 2016

Comment author: lebedev

This has been merged as #29.

@dbuenzli

This comment has been minimized.

Copy link
Contributor

commented Mar 15, 2019

This can be closed.

@vicuna

This comment has been minimized.

Copy link
Author

commented Mar 15, 2019

Thanks!

@vicuna vicuna closed this Mar 15, 2019

@vicuna vicuna added the feature-wish label Mar 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.