-
Notifications
You must be signed in to change notification settings - Fork 30k
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
FR: History support for repl #394
Comments
There are a few repl alternatives in npm that you can use for more advanced features, including replpad. Unless others pipe up on this, this issue will be closed because it's not really actionable without code. |
Having history support would be nice, because a lot of times I close the REPL and I open it the next day to try something out based on what I tried before. |
this is one of those cases where providing code in the form of a pull request can actually make proper discussion happen, otherwise it'll be a dead end with people giving |
I just noticed that appeared another PR for this. Mine for this #442. |
@rvagg just to bump this, that it is not lost between issues, because i am very interested to have something like this. |
Not my call, I'm staying out of this one as I'm not overly enthused about the way this is being implemented (not bothered enough to actually contribute or comment though!). You'll have to do some campaigning to other collaborators, see the README for the current list and see if you can get enough agreement to get something landed. |
Is anyone strongly opposed to closing this and related issues/PRs? There seems to be enough userland support for REPL history/logging. |
It will be nice to have ability to save iojs repl session over exits. It could save simply as many programs do in ~/.iojs_session.
The text was updated successfully, but these errors were encountered: