0cb2057a76
Usually the current behavior is best: You are dropped in a REPL with the package(s) you are working on already available. As you are working on them, you recompile individual files and your changes become available. However, I've found that there are some occasions when this is not desireable, e.g.: When you are working on something and have broken the test suite intermittently, it becomes impossible to start a new REPL. Not sure how the yes-or-no-p question should be phrased, its negation may be better? Change-Id: I6a37ebc02f3121f628fc9206e0de650851824cd6 Reviewed-on: https://cl.tvl.fyi/c/depot/+/8415 Autosubmit: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI Reviewed-by: tazjin <tazjin@tvl.su> |
||
|---|---|---|
| .. | ||
| checks | ||
| cheddar | ||
| emacs-pkgs | ||
| magrathea | ||
| nixery | ||
| nsfv-setup | ||
| releases | ||
| rust-crates-advisory | ||
| crfo-approve.nix | ||
| depot-deps.nix | ||
| depotfmt.nix | ||
| eprintf.nix | ||
| fetch-depot-inbox.nix | ||
| gerrit-cli.nix | ||
| gerrit-update.nix | ||
| hash-password.nix | ||
| perf-flamegraph.nix | ||