-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Closed
Labels
UXThe way in which users interact with Nix. Higher level than UI.The way in which users interact with Nix. Higher level than UI.error-messagesConfusing messages and better diagnosticsConfusing messages and better diagnosticslanguageThe Nix expression language; parser, interpreter, primops, evaluation, etcThe Nix expression language; parser, interpreter, primops, evaluation, etc
Description
Is your feature request related to a problem? Please describe.
Whenever nix --show-trace prints a long stack trace, I have to scroll up the terminal a lot to find the code line which triggered the error.
Describe the solution you'd like
Reverse the order of the printed stack
Additional context
From my experience most other programming languages' stack traces are printed in a way so that the code line which triggered the error is printed last.
This makes sense, because it is the most relevant part of the information and the first place to look for when doing debugging.
Nix, for some reason, does it the other way round which seems impractical and requires scrolling up the terminal
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
UXThe way in which users interact with Nix. Higher level than UI.The way in which users interact with Nix. Higher level than UI.error-messagesConfusing messages and better diagnosticsConfusing messages and better diagnosticslanguageThe Nix expression language; parser, interpreter, primops, evaluation, etcThe Nix expression language; parser, interpreter, primops, evaluation, etc