fix directory tree renderings

This commit is contained in:
Valentin Gagarin 2022-08-04 13:50:44 +02:00
parent 3df1ee2ba5
commit 8cec32e7f5

View file

@ -19,27 +19,27 @@ Examples:
- a directory with contents - a directory with contents
/nix/store/<hash>-hello-2.10 /nix/store/<hash>-hello-2.10
├── bin ├── bin
│   └── hello │   └── hello
└── share └── share
├── info ├── info
│   └── hello.info │   └── hello.info
└── man └── man
└── man1 └── man1
└── hello.1.gz └── hello.1.gz
- a directory with relative symlink and other contents - a directory with relative symlink and other contents
/nix/store/<hash>-go-1.16.9 /nix/store/<hash>-go-1.16.9
├── bin -> share/go/bin ├── bin -> share/go/bin
├── nix-support/ ├── nix-support/
└── share/ └── share/
- a directory with absolute symlink - a directory with absolute symlink
/nix/store/d3k...-nodejs /nix/store/d3k...-nodejs
└── nix_node -> /nix/store/f20...-nodejs-10.24. └── nix_node -> /nix/store/f20...-nodejs-10.24.
A bare file or symlink can be a root file system object. A bare file or symlink can be a root file system object.
Examples: Examples:
@ -53,13 +53,13 @@ Examples:
- an arbitrarily symlinked file may change or not exist at all - an arbitrarily symlinked file may change or not exist at all
/nix/store/<hash>-foo /nix/store/<hash>-foo
└── foo -> /home/foo └── foo -> /home/foo
- if a symlink to a store path was not automatically created by Nix, it may be invalid or get invalidated when the store object is deleted - if a symlink to a store path was not automatically created by Nix, it may be invalid or get invalidated when the store object is deleted
/nix/store/<hash>-bar /nix/store/<hash>-bar
└── bar -> /nix/store/abc...-foo └── bar -> /nix/store/abc...-foo
Nix file system objects do not support [hard links][hardlink]: Nix file system objects do not support [hard links][hardlink]:
each file system object which is not the root has exactly one parent and one name. each file system object which is not the root has exactly one parent and one name.