{{ message }}
Repository navigation
Command Line Options - relative paths inconsistent #37
Description
Describe the bug
The path for -hyde-yaml-dir and -hyde-src-root is relative to the directory containing the file being processed. i.e.
hyde ./include/psutil/safe_cast.hpp -hyde-src-root=../../include -hyde-yaml-dir=../../docs/include
Here the path ../../include is relative to ./include/psutil/ and not the current working directory.
Metadata
Metadata
Assignees
Labels
No labels
Activity
fosterbrereton commentedon Aug 7, 2019
Am I understanding correctly that you'd like the relative paths to be from the current working directory? That means you must navigate to a specific path before running the tool in order for it to function. I based the relative paths off the source file being processed because then the tool can be run regardless of the current working directory, which seemed the more flexible option.
sean-parent commentedon Aug 7, 2019
Let's say I have:
include/library/file.hpp
include/library/sub/other.hpp
I would have to have two separate roots for each of those. That is a bit of a pain. Normally a path specified on the command line is relative to the current working directory, and a path in a file (like a config file, header file, html file, etc.) is relative to that file. Having the path be relative to some other file is weird and confusing.
Fix for issue #37 - removing the cwd being set to the source file bei…
Path autodetection (#41)