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.

Sign up for GitHub

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

Jump to bottom

Need a visual indicator of the last executed code/next to be executed code in data science "mode" #3762

Closed
gramster opened this issue Dec 3, 2018 · 3 comments
Closed

Need a visual indicator of the last executed code/next to be executed code in data science "mode" #3762

gramster opened this issue Dec 3, 2018 · 3 comments
Assignees
@rchiodo

Comments

@gramster
Copy link
Member

gramster commented Dec 3, 2018

If you do a "Run cell" it would be nice to have some indication of what code was run and where the next cell starts. For example, if you import a notebook and then run cells in succession using Run Cell (not Run All Cells) it can be easy to miss a cell because you don't always see where you are. Even having the "Run Cell" in a brighter color would help to demarcate the boundaries better. This is exacerbated by the fact that the "Run Cell" code lenses fade in as you scroll new text into view so may not be immediately apparent.

Environment data

  • VS Code version: XXX
  • Extension version (available under the Extensions sidebar): 2018.11.0
  • OS and version: MacOS
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
  • Relevant/affected Python packages and their versions: XXX
@ronglums
Copy link
Contributor

ronglums commented Dec 4, 2018

Check Spyder to see how the last executed code cell is highlighted in the editor.

@rchiodo rchiodo self-assigned this Apr 11, 2019
@ronglums
Copy link
Contributor

Try the light grey color.

image

@ronglums
Copy link
Contributor

Also, perhaps a line separation between cells.

rchiodo referenced this issue in microsoft/vscode-python Apr 12, 2019
@rchiodo
Add current cell highlight (#5219)
d65f0eb 
For #3542

<!--
  If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.:
    - [x] ~Has unit tests & system/integration tests~
-->
- [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
- [x] Title summarizes what is changing
- [x] Has a [news entry](https://github.com/Microsoft/vscode-python/tree/master/news) file (remember to thank yourself!)
- [ ] Has sufficient logging.
- [ ] Has telemetry for enhancements.
- [ ] Unit tests & system/integration tests are added/updated
- [ ] [Test plan](https://github.com/Microsoft/vscode-python/blob/master/.github/test_plan.md) is updated as appropriate
- [ ] [`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package-lock.json) has been regenerated by running `npm install` (if dependencies have changed)
- [ ] The wiki is updated with any design decisions/details.
@rchiodo rchiodo closed this as completed Apr 24, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 22, 2019
@microsoft microsoft unlocked this conversation Nov 14, 2020
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 14, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rchiodo rchiodo

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gramster @rchiodo @ronglums