Skip to content

Fix markdown in documentation in 'Manually specifying an interpreter' #511

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
Closed
DonJayamanne opened this issue Jan 2, 2018 · 3 comments
Closed

Fix markdown in documentation in 'Manually specifying an interpreter' #511

DonJayamanne opened this issue Jan 2, 2018 · 3 comments
Assignees
@brettcannon
Labels
bug Issue identified by VS Code Team member as probable bug good first issue
Milestone
January 2018

Comments

@DonJayamanne
Copy link

The markdown doesn't seem to be correctly formatted:
https://code.visualstudio.com/docs/python/environments#_manually-specifying-an-interpreter
@DonJayamanne DonJayamanne added awaiting 2-PR bug Issue identified by VS Code Team member as probable bug labels Jan 2, 2018
@DonJayamanne DonJayamanne added this to the January 2018 milestone Jan 2, 2018
@gaurikholkar-zz
Copy link

gaurikholkar-zz commented Jan 9, 2018 •
edited
Loading

Can I pick this up?

@DonJayamanne
Copy link
Author

Anyone can pick an issue and submit a PR. specially those takes with 'Good first issue'.
So to answer your question, most certainly yes.

@brettcannon brettcannon assigned qubitron and brettcannon and unassigned qubitron Jan 9, 2018
@brettcannon
Copy link
Member

Sorry, @gaurikholkar , but we went ahead and fixed this while dealing with other doc bugs that were in the same file.

Fixed in microsoft/vscode-docs#1350 .

@brettcannon brettcannon mentioned this issue Jan 29, 2018
Closed
38 tasks
@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@brettcannon brettcannon

Labels
bug Issue identified by VS Code Team member as probable bug good first issue
Projects
None yet
Milestone
January 2018
Development

No branches or pull requests
4 participants
@brettcannon @DonJayamanne @gaurikholkar-zz @qubitron