about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-11-14 23:16:21 -0800
committerKartik K. Agaram <vc@akkartik.com>2015-11-14 23:16:21 -0800
commit7ecb3374340c02cc2c54abf4a5d4a617f362b4c4 (patch)
treea8bf285e11d1968fdc61457023d0adc5f95693af
parent3a982057f8b8c8fbca6a95e0f7043f9f0decb5f3 (diff)
downloadmu-7ecb3374340c02cc2c54abf4a5d4a617f362b4c4.tar.gz
2440
In debugging 2438, I spent a while going around in circles trying to
decide if there was a stray overload of 'interactive'. Part of the
problem was the hacky delete of a recipe just above. Stop doing that.
-rw-r--r--091run_interactive.cc3
1 files changed, 1 insertions, 2 deletions
diff --git a/091run_interactive.cc b/091run_interactive.cc
index f871275a..25e02836 100644
--- a/091run_interactive.cc
+++ b/091run_interactive.cc
@@ -78,14 +78,13 @@ bool run_interactive(long long int address) {
   }
   string command = trim(strip_comments(read_mu_string(address)));
   if (command.empty()) return false;
-  Recipe.erase(get(Recipe_ordinal, "interactive"));
   Name[get(Recipe_ordinal, "interactive")].clear();
   run_code_begin();
   // don't kill the current routine on parse errors
   routine* save_current_routine = Current_routine;
   Current_routine = NULL;
   // call run(string) but without the scheduling
-  load(string("recipe interactive [\n") +
+  load(string("recipe! interactive [\n") +
           "local-scope\n" +
           "screen:address:screen <- next-ingredient\n" +
           "$start-tracking-products\n" +