# A page the self-test reads

Each of these names a path that resolves: `crates/demo/src/lib.txt`,
`crates/demo/src/lib.txt:3`, `crates/demo/src/lib.txt:2-3`, `crates/demo/`,
`crates/demo`, `crates/demo/src/{lib,wire}.txt` and `scripts/demo --check`.

None of these is a path: `cargo test -p demo`, `crates`, `src/gone.txt`,
`https://example.com/crates/gone.txt`, `crates/*/gone.txt`, `plan/<id>.md`,
`crates/demo/src/gone.txt::item` and ``a `crates/demo/src/gone.txt` span``.

A span can wrap onto the next line, as `cargo
test` does, and the one after it still pairs: `crates/demo/src/gone.txt`.

- `crates/demo/src/lib.txt:9`
- `crates/demo/src/lib.txt:2-9`
- `crates/demo/src/{lib,gone}.txt`
- `crates/demo/src/lib.txt/`
- `scripts/gone --check`

```sh
# A fence runs on past a blank line.

cat `crates/demo/src/gone.txt`
```

````md
```
`crates/demo/src/gone.txt`
```
````

A path can start at a workspace member: `demo/src/lib.txt:3`,
`demo/src/{lib,wire}.txt` and `demo/` resolve, and `demo/src/gone.txt` is
flagged. A bare name, `lib.txt`, is skipped, and so is `other/src/lib.txt`,
since `tools/other` is not a member.