[Nix#9531] nix repl
tab completion does not print errors. Uncanny. #91
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#91
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Upstream-Issue: NixOS/nix#9531
Describe the bug
Tab completion is essential for being productive in the repl.
When an expression does not evaluate, tab completion just "ends" without any indication that something went wrong, as if it's an empty attribute set or a primitive value.
This always confuses me for a short amount of time, until I realise that I need to hit enter to see the error.
Please don't stall my brain.
Steps To Reproduce
Expected behavior
In my experience with bash completing Nix attribute paths, it's tricky to get them right, so that they balance laziness and minimal completion steps.
It seems that the missing piece here is just to allow printing the error, or actively print the error.
While it's possible to go overboard and have more intricate rules that complete more faster, that runs the risk of producing the error too soon, before the user realises which attribute they entered. Hence the 2 s below.
nix-env --version
outputAdditional context
Priorities
Add 👍 to issues you find important.