Actions
Bug #5940
closedShould we resolve implicit (or explicit) file: URIs for the -o option?
Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2023-03-24
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
11, 12, trunk
Fix Committed on Branch:
11, 12, trunk
Description
The documentation is clear that -o
is a filename, but...
- If a user specifies
-u
, it's very tempting to specify afile:
URI for-o
- Even if a user doesn't specify
-u
, we detectfile:
URIs on inputs implicitly, shouldn't we do the same for the output?
Please register to edit this issue
Actions