Skip to content

Tracking paths to error locations #138

@mmottl

Description

@mmottl

My directory structure is as follows:

jbuild
jbuild-workspace
src/
  jbuild
  ...
examples/
  foo.ml
  jbuild
  ...

src contains a library and examples example applications. If I go to the examples directory and issue a build command from there (e.g. from an editor), an error in example foo.ml would be reported using location examples/foo.ml. This is a problem for inferring correct error locations. The editor does not know where the root of this path is, because we are in a (potentially even deeper) subdirectory.

Could you please print the absolute path of the root for error messages for a particular build when jbuilder is invoked so editors can infer the correct path? E.g. Vim allows you to pattern match on the build output to keep track of directory stacks for correct errors locations. A somewhat unique string should be used to correctly identify this location message, preferably an existing make-like Entering directory message that Vim or Emacs already understand.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions