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

Add command to reset the REPL #54

Closed
laurentpetit opened this issue Mar 15, 2015 · 8 comments
Closed

Add command to reset the REPL #54

laurentpetit opened this issue Mar 15, 2015 · 8 comments
Assignees

Comments

@laurentpetit
Copy link
Member

Original issue 11 created by laurentpetit on 2009-11-08T13:03:22.000Z:

Currently the launch shortcut can evaluate to the REPL. In some cases,
user may want to reset the REPL to unload previously evaluated expressions.
Add a command to the REPL console to reset the REPL thread.

@laurentpetit
Copy link
Member Author

Comment #1 originally posted by laurentpetit on 2010-04-18T21:00:49.000Z:

<empty>

@laurentpetit
Copy link
Member Author

Comment #2 originally posted by laurentpetit on 2010-10-15T09:57:45.000Z:

Rather than resetting the REPL, why not restart it, or kill it and start a new one?

I'd suggest WONTFIX for this, given those simpler alternatives…

@laurentpetit
Copy link
Member Author

Comment #3 originally posted by laurentpetit on 2010-10-15T11:03:09.000Z:

Hmm, I need some more time to think about it. e.g. if resetting namespaces takes far less time than restarting a repl, there could still be some value into this.

I lower the priority.

@laurentpetit
Copy link
Member Author

Comment #4 originally posted by laurentpetit on 2010-10-19T23:06:53.000Z:

More to think about: it's not really possible to do a full reset, if we're talking about really returning the REPL to its un-interacted-with state. Java classes can't be un-initialized, threads that were started running uninterruptable code can't be stopped (safely), etc. etc.

@laurentpetit
Copy link
Member Author

Comment #5 originally posted by laurentpetit on 2010-10-19T23:07:27.000Z:

<empty>

@laurentpetit
Copy link
Member Author

Comment #6 originally posted by laurentpetit on 2010-10-19T23:14:15.000Z:

Yes, so the semantics "reset REPL" don't hold. It would be more a command to "prune" namespaces from vars ... hmmm, not high priority unless a real need with an appropriate (and legitimate) use case happens, indeed ...

@laurentpetit
Copy link
Member Author

Comment #7 originally posted by laurentpetit on 2011-02-27T19:55:09.000Z:

Yes, a proper 'reset' REPL is difficult (but not impossible) to implement. Also, I think not really necessary. I think a 'restart' REPL would be very convenient. As it stands now, it is a three step process to restart a REPL: 1) kill the console, 2) close the CCW REPL view (not necessary, but I like to keep my workspace tidy) and 3) start a new REPL. It would be nice to issue a single command for all three of these steps.

@laurentpetit
Copy link
Member Author

Comment #8 originally posted by laurentpetit on 2011-03-08T20:03:09.000Z:

Yes, I'd say a "Restart REPL" command in the REPLView's toolbar makes a lot more sense. Closing this and opening a new ticket for a restart REPL enhancement.

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

No branches or pull requests

1 participant