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
Evaluate only the selected code #328
Comments
To be clear, all of the cell is being evaluated, but only the last line will return something into the output at the moment. Implementing this behavior would break Jupyter parity. |
Is this what you are talking about? I am sorry I do not know about Jupyter Parity, what is it? |
By the way that is what I meant when I said last line is being evaluated, I meant that only the final output of a cell is being showed. |
Ah yes, "jupyter parity" is kind of an unclear term. I meant that as a starting point we are trying to reach feature parity with the Jupyter notebook to some extent, and what we have now is pretty fundamental to the current story. For us, reaching parity means having a lot of the workflow feel easy enough for Jupyter users. We are likely not going to port over all features. Unfortunately we don't have much of a doc to cover what this means, but given our focus on the ergonomics of scientific computing, we've mostly dialed into the actual work experience. |
Right now, when i click anywhere in a cell and press
Shift+Enter
, the last line of that cell is being evaluated. I think it would be better if we can evaluate only some part of the cell by selecting the required part of a cell. If nothing is selected, then the behaviour would be normal(evaluating the last line).I think this feature would be very useful as it is taking a lot of steps to press
ESC
and thenb
and then write code just so that in future that code can be evaluated too.The text was updated successfully, but these errors were encountered: