docs(manual): move command examples before options - #16326
Open
djairofilho wants to merge 1 commit into
Open
Conversation
djairofilho
force-pushed
the
docs/manual-move-classic-command-examples
branch
from
August 19, 2026 03:36
13323e3 to
62d812c
Compare
Assisted-by: Codex (GPT-5)
djairofilho
force-pushed
the
docs/manual-move-classic-command-examples
branch
from
August 20, 2026 00:39
62d812c to
830a9f9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Classic command pages currently place their examples after long lists of
options and environment variables. This makes practical usage harder to find
when scanning the documentation.
Move the examples directly after each command description so they are visible
before the reference material.
Context
This change reorders the existing example sections in 24 classic command
pages. It does not modify the examples or add new documentation.
The manual was validated with:
nix build .#nix-manual --no-linkCloses #10717
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.