set: Don't treat toplevel scope the same as global

When using the `set` command with the -l flag, if we're at the top
level, create a temporary local scope. This makes query/assignment
behavior be consistent with the value-printing behavior.

This works by marking the current block as needing to pop the
environment if a local scope was pushed. I assume this is safe to do. I
also assume the current block is the right one to modify, rather than
trying to walk up the stack to the root.

1 files changed, 6 insertions, 0 deletions

diff --git a/env.h b/env.h
index d1a40f7d..e886a5b2 100644
--- a/env.h
+++ b/env.h
@@ -199,6 +199,12 @@ void env_push(bool new_scope);
 */
 void env_pop();
 
+/**
+  Push the variable stack if the current scope is the global scope. Returns
+  whether it pushed a scope.
+*/
+bool env_ensure_local_scope();
+
 /** Synchronizes all universal variable changes: writes everything out, reads stuff in */
 void env_universal_barrier();