Invert behaviour of the debugger's `--ignore-try` #666

New issue

Closed

opened 2025-02-11 00:07:27 +00:00 by jade · 1 comment

jade commented

2025-02-11 00:07:27 +00:00

Owner

The debugger catches the wrong things if you use it on nixpkgs because of constant tryEval calls. This sucks. We should just invert the behaviour: make --ignore-try the default and --no-ignore-try the alternative. And maybe print an informational message when we yeet through a tryEval call?

Also, um, why is ignore-try an evaluator setting whereas debugger is a CLI flag? This causes the documentation in man pages to be bad since try-eval is nowhere to be seen.

The debugger catches the wrong things if you use it on nixpkgs because of constant `tryEval` calls. This sucks. We should just invert the behaviour: make `--ignore-try` the default and `--no-ignore-try` the alternative. And maybe print an informational message when we yeet through a tryEval call? Also, um, why is ignore-try an evaluator setting whereas debugger is a CLI flag? This causes the documentation in man pages to be bad since try-eval is nowhere to be seen.

jade added the

Area/evaluator

E/easy

E/help wanted

labels

2025-02-11 00:07:27 +00:00

jade referenced this issue

2025-02-13 20:48:03 +00:00

Allow showing relevant settings inside of man pages next to options in the CLI framework #672

jade added the

Area/repl/debugger

label

2025-03-31 20:14:48 +00:00

lix-bot commented

2025-06-26 17:19:53 +00:00

Member

This issue was mentioned on Gerrit on the following CLs:

commit message in cl/3488 ("repl: default to turning off ignore-try")

This issue was mentioned on Gerrit on the following CLs: * commit message in [cl/3488](https://gerrit.lix.systems/c/lix/+/3488) ("repl: default to turning off ignore-try")