1
0
Fork 0
mirror of https://github.com/NixOS/nix.dev.git synced 2024-10-18 14:32:43 -04:00

updated the context for the installation script to match the example … (#793)

* updated the context for the installation script to match the example for steps outlined

Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
This commit is contained in:
Rob Thomas 2023-11-09 11:39:00 -06:00 committed by GitHub
parent 0d770fce2e
commit fcac94d552
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -17,7 +17,7 @@ Declarative shell environments allow you to
### What will you learn?
In the {ref}`ad-hoc-envs` tutorial, we looked at imperatively creating shell environments using `nix-shell -p`, for when we need a quick way to access some tools without having to install them globally.
In the {ref}`ad-hoc-envs` tutorial, we looked at imperatively creating shell environments using `nix-shell -p`, when we need a quick way to access tools without having to install them globally.
We also saw how to execute that command with a specific Nixpkgs revision using a Git commit as an argument, to recreate the same environment used previously.
In this tutorial we'll take a look how to create reproducible shell environments given a declarative configuration in a {term}`Nix file`.
@ -32,7 +32,7 @@ In this tutorial we'll take a look how to create reproducible shell environments
## Entering a shell with Python installed
Suppose we a development environment in which Python 3 was installed.
Suppose we want a development environment in which Git, Neovim, and Node.js were installed.
The simplest possible way to accomplish this is via the `nix-shell -p` command:
```
$ nix-shell -p git neovim nodejs