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

Interactive Window (python) history only captures from input box, not from e.g, Run Selection in Interactive Window #11468

Closed
1 of 2 tasks
paulmadejong opened this issue Sep 27, 2022 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged

Comments

@paulmadejong
Copy link

paulmadejong commented Sep 27, 2022

Applies To

  • Notebooks (.ipynb files)
  • Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

When scrolling through history using the up and down arrows, only inputs that were inputted using the input box of the interactive window are shown. I would appreciate that code that was entered using "Run Selection/Line in Interactive Window" (or any other way of copying code from Editor into the Interactive Window) would also be part of the history. This was suggested in #8658 but the issue was closed. Is this a bug or intentional?

Also, the ability to alter run cell blocks as with Jupiter in a browser would be helpful.

VS Code Version

1.71.2 (Universal)

Jupyter Extension Version

v2022.8.1002431955

Jupyter logs

none

Coding Language and Runtime Version

Python 3.10.6 and IPython 7.26.0

Language Extension Version (if applicable)

v2022.14.0

Anaconda Version (if applicable)

No response

Running Jupyter locally or remotely?

Local

@paulmadejong paulmadejong added bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged labels Sep 27, 2022
@roblourens roblourens assigned rebornix and unassigned roblourens Sep 27, 2022
@amunger
Copy link
Contributor

amunger commented Sep 27, 2022

I think it's actually covered by microsoft/vscode#129081 (which was also closed) since it needs to be implemented in core.

@amunger amunger closed this as completed Sep 27, 2022
@paulmadejong
Copy link
Author

I think it's actually covered by microsoft/vscode#129081 (which was also closed) since it needs to be implemented in core.

Yes that’s the exact same request. Didn’t find it myself so thanks for pointing me there. Hope they work on it in core to improve usability!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

4 participants