[superseded] --listFullPaths:off now shows paths relative to cwd

[timotheecour]

the previous behavior never made sense to me as it showed a relative path that wasn't relative to current dir (so couldn't be easily opened)
now you can easily open either via clicking on it (if your terminal supports it) or via open somerelativepath etc

likewise, this is especially true if nim command was run programmatically, in which case user has even less context as to how to turn project path to an actual path

[Araq]

Looks fine to me once the tests are green.

[timotheecour]

yikes, 110 tests failed, and maybe for a good reason (ie project makes sense for testing purposes but not for cmdline usage); how about this:

new flag:
--msgpaths:{full,relative,project,basename}

with default to --msgpaths:full (ie same semantics as current default)
testament shall use: --msgpaths:project (ie same semantics as currently used in testament)

• if --listFullPaths, --listFullPaths:on is passed => implies --msgpaths:full
• if --listFullPaths:off is passed => implies --msgpaths:relative (change of behavior; alternatively we can keep old behavior, ie implies --msgpaths:project)
• and we un-document --listFullPaths

[Araq]

There is already tests/config.nims with these options:

switch("path", "$nim/testament/lib") # so we can `import stdtest/foo` in this dir

## prevent common user config settings to interfere with testament expectations
## Indifidual tests can override this if needed to test for these options.
switch("colors", "off")
switch("listFullPaths", "off")
switch("excessiveStackTrace", "off")

I don't know if that helps, I'm tired...

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. If you think it is still a valid PR, please rebase it on the latest devel; otherwise it will be closed. Thank you for your contributions.