lix-project/lix
18
38
Fork 14
Code Issues 288 Code Review (Gerrit) Projects 1 Releases Wiki Activity

docs: clarify how the different kinds of installables are selected

Browse source 
Change-Id: I146736bb97ebe035e04be69ce9fb60a557e38c6c
This commit is contained in:
Qyriad 2024-04-29 08:15:16 -06:00
parent 194ba8a02f
commit bd2619868c
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/nix/nix.md
View file

@ -59,9 +59,13 @@ These are command line arguments that represent something that can be realised i
The following types of installable are supported by most commands: The following types of installable are supported by most commands:
- [Flake output attribute](#flake-output-attribute) (experimental) - [Flake output attribute](#flake-output-attribute) (experimental)
- This is the default
- [Store path](#store-path) - [Store path](#store-path)
- This is assumed if the argument is a Nix store path or a symlink to a Nix store path
- [Nix file](#nix-file), optionally qualified by an attribute path - [Nix file](#nix-file), optionally qualified by an attribute path
- Specified with `--file`/`-f`
- [Nix expression](#nix-expression), optionally qualified by an attribute path - [Nix expression](#nix-expression), optionally qualified by an attribute path
- Specified with `--expr`/`-E`
For most commands, if no installable is specified, `.` is assumed. For most commands, if no installable is specified, `.` is assumed.
That is, Nix will operate on the default flake output attribute of the flake in the current directory. That is, Nix will operate on the default flake output attribute of the flake in the current directory.