-
Notifications
You must be signed in to change notification settings - Fork 40
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
Feature: adding an edit command #77
Comments
I like the idea. It could pull from |
Not really. Paste inserts new content into the file (and icr executes it then). Edit will give you a way to edit that file. So it will be possible to remove previously inserted "bad commands". But, i don't know, that may an overhead.... |
So that file could look something like
This edit would probably need a way to denote what can't be removed. Maybe a comment appended to the end of those lines? Then again, now that I think about it. Would people want this as a feature vs just opening up a file and throwing some test code in that, then running it? If you're just talking about un-doing a bad command, that may go along with my initial commit I started for adding |
Right, this is what I'm afraid of as well. If we give a way to the users a direct way to edit the file, anyone can accidentally break a hole session while removing I regularly use vicr for multi-line content, but sometimes just need to execute one line of code to test something, and icr is faster for this. So that's why i see some mixed approach (repl & editor) helpful. Probably |
Oh nice. I hadn't seen vicr until now. A mixed approach would be nice. Maybe we take this whole thing back to the drawing board, and look at icr from the ground up? Crystal has come a long way since the icr inception, so maybe there's new stuff we can take advantage of? |
Pulling this in from #75 (comment)
@veelenga wrote :
The text was updated successfully, but these errors were encountered: