Ian Manske 03ee54a4df Fix try not working with let, etc. (#13885) ... # Description Partialy addresses #13868. `try` does not catch non-zero exit code errors from the last command in a pipeline if the result is assigned to a variable using `let` (or `mut`). This was fixed by adding a new `OutDest::Value` case. This is used when the pipeline is in a "value" position. I.e., it will be collected into a value. This ended up replacing most of the usages of `OutDest::Capture`. So, this PR also renames `OutDest::Capture` to `OutDest::PipeSeparate` to better fit the few remaining use cases for it. # User-Facing Changes Bug fix. # Tests + Formatting Added two tests.		2024-09-23 06:44:25 -05:00
..
sys	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
complete.rs	Fix try not working with let, etc. (#13885)	2024-09-23 06:44:25 -05:00
exec.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
mod.rs	Rewrite run_external.rs (#12921)	2024-05-23 02:05:27 +00:00
nu_check.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
ps.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
registry_query.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
run_external.rs	Fix try not working with let, etc. (#13885)	2024-09-23 06:44:25 -05:00
uname.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00
which_.rs	Change the usage misnomer to "description" (#13598)	2024-08-22 12:02:08 +02:00