Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(request) implement an UNSET ALL that works like UNLOCK ALL #261

Open
Dunbaratu opened this issue Nov 20, 2013 · 2 comments
Open

(request) implement an UNSET ALL that works like UNLOCK ALL #261

Dunbaratu opened this issue Nov 20, 2013 · 2 comments

Comments

@Dunbaratu
Copy link
Contributor

It wold be handy if there was an UNSET ALL that cleared the value of every variable.

At the moment I'd like it as a workaround to the loading from on-rails problem. (If you have no variable context being kept alive in the persistence file, then the bug does not occur, so make sure to UNSET ALL just before going on-rails).

But I can see other cases where it would be handy - like to test a script from the beginning again and making sure it starts from a clean slate.

@Dunbaratu
Copy link
Contributor Author

Alternatively, if the act of rebooting the machine caused the variables to clear, that would work too. (It doesn't, by the way, and I don't know if that's a bug or intentional. If you "set x to 5." and then "reboot." and then after rebooting do "print x." it still says "5".

@a1270
Copy link
Contributor

a1270 commented Nov 20, 2013

Seems system variables and user-defined ones are stored in the same list. Have to think about how to deal with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants