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

Shift-enter should also advance cursor to the next line #13495

Closed
arencambre opened this issue Aug 18, 2020 · 6 comments
Closed

Shift-enter should also advance cursor to the next line #13495

arencambre opened this issue Aug 18, 2020 · 6 comments
Labels
feature-request Request for new features or functionality

Comments

@arencambre
Copy link

arencambre commented Aug 18, 2020

When I hit shift-enter, I am intending to run the current line or selection. I would like for the Python extension to also advance the cursor to the next line.

Advancing the cursor to the next line is just helpful. It is not common that I wish to re-run the current line after pressing shift-enter. More typically, I want to run several lines in a row. Allowing shift-enter makes this more intuitive.

This should also apply even when you are running multiple, selected lines. It will necessarily cause the selection to be un-selected since the cursor will need to move to the line right after the end of the selection. In my experience, it is rare that I would want to manually, repeatedly run multiple, selected lines. Rather, the most common occurrence currently is, after I hit shift-enter, I have to down-arrow through the end of the selection to run the next desired line. Because the selection disappeared as soon as I hit down-arrow, I lose the obvious, visual reference for end of line, which makes it even harder. If the cursor just went to the first line after the selection, that would be helpful.

RStudio has the same "skip to the next line after shift-enter" behavior. I find it useful.

@arencambre arencambre added triage-needed Needs assignment to the proper sub-team feature-request Request for new features or functionality labels Aug 18, 2020
@karthiknadig
Copy link
Member

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Aug 18, 2020
@andycraig
Copy link

This was one of the requests in #4978. I would love this feature.

@arencambre
Copy link
Author

#4798 is also a great idea.

I could see this one being implemented first with #4798 being a follow-on.

@luabud
Copy link
Member

luabud commented Sep 23, 2020

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature.

@luabud luabud closed this as completed Sep 23, 2020
@ghost ghost removed the needs decision label Sep 23, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2021
@anthonykim1
Copy link

This is available with new 'Smart Send' Feature #21838
There is also setting to toggle this on/off.

@luabud
Copy link
Member

luabud commented Dec 14, 2023

This is the setting btw, "Enable REPL Smart Send"

image

(or python.REPL.enableREPLSmartSend if you're adding settings to settings.json)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

5 participants