View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003298 | Avdump2 / autocreq | Bug Report | public | 2019-01-04 19:35 | 2019-01-05 09:09 |
| Reporter | msoltyspl | Assigned To | DvdKhl | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | Chrome | OS | Windows | OS Version | 7 and 10 |
| Summary | 0003298: Options such as --Exp= require absolute paths | ||||
| Description | As in subject, there seems to be no way to export data to current directory (or relative path) without providing absolute path. | ||||
| Steps To Reproduce | 1) Put avdump2 in c:\tools (and add it to PATH) 2) cd c:\tmp 3) AVDump2CL.exe --PrintEd2kLink --Exp="ed2k.txt" -t -a . I'd expect ed2k.txt to be in c:\tmp, but it will be in c:\tools instead. Same if we do --Exp=".\ed2k.txt" | ||||
| Tags | No tags attached. | ||||
|
|
It uses the path where the executable is for historical reasons. I'd prefer using the current working directory as well but I'd imagine many would complain. That said, there is an option to use the working directory instead: "--UseCWD" |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-01-04 19:35 | msoltyspl | New Issue | |
| 2019-01-04 19:56 | CDB-Man | Assigned To | => CDB-Man |
| 2019-01-04 19:56 | CDB-Man | Status | new => assigned |
| 2019-01-04 19:57 | CDB-Man | Assigned To | CDB-Man => |
| 2019-01-04 19:57 | CDB-Man | Assigned To | => DvdKhl |
| 2019-01-05 09:09 | DvdKhl | Note Added: 0004330 | |
| 2019-01-05 09:09 | DvdKhl | Note Edited: 0004330 |
