Hamza 19f40e6554 The two file tests ask which file, not how the OS says it is missing ...

Review of #3849: both tests asserted `stderr.contains("No such file")`, which
is the Unix wording. On Windows the same error reads "The system cannot find
the file specified. (os error 2)", so `test (windows-latest)` failed on them.

Neither test is about the wording. What they are about:

- `a_flag_that_takes_no_value_does_not_swallow_the_file`: the error is about
  `missing.pdf`, and is not "check-one: missing file" -- the file reached the
  command instead of being eaten as `--edit`'s operand.
- `a_file_whose_name_starts_with_dashes_is_still_reachable`: the error names the
  file the command could not open (`missing.pdf`, or `./--dash.pdf` for the
  `info` case), and is not a usage error about a value or an unknown option.

Both now assert exactly that, plus the absence of our own usage phrases. Every
string they match is one this CLI prints, so the OS has no say in it.

2026-10-22 21:21:00 +05:00

..

src

cli: the argument bugs photocraft#7071 lists are live here too

2026-10-21 18:45:04 +05:00

tests

The two file tests ask which file, not how the OS says it is missing

2026-10-22 21:21:00 +05:00

build.rs

CLI: pdfcraft-cli.exe carries a Windows version resource (#598)

2026-10-09 19:09:23 -04:00

Cargo.toml

cli: info names the standard a document declares (#3328)

2026-10-18 17:06:29 -04:00