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

Perf. Issues instructions: Tell us how to find "Developer:"? #134599

Closed
drscotthawley opened this issue Oct 7, 2021 · 3 comments
Closed

Perf. Issues instructions: Tell us how to find "Developer:"? #134599

drscotthawley opened this issue Oct 7, 2021 · 3 comments
Assignees

Comments

@drscotthawley
Copy link

drscotthawley commented Oct 7, 2021

It's been requested that I perform a profile to accompany my separate issue. The instructions say

"Execute the Developer: Show Running Extensions Command. This command opens an editor with all the running extensions."

but do not explain how to find "Developer:". Presumably Microsoft employees know exactly where this is, but I have searched in the various menus (File, Edit, Selection, View, Go, Run, Terminal, Help), Settings, three-dots, etc. as well as the buttons available in the extension view, and cannot find it. Single-clicking things, Right-clicking things... I've been unsuccessful.

Also, "Help > Toggle Developer Tools" does not seem to provide the "Running Extensions" in any of the various tabs (Elements, Console, Sources, Network, Performance, Memory, Application, Security, Lighthouse) or triple-dot menus or drop-downs that I can find (e.g. "More tools > Developer resources" does not have it.)

My request is that these documentations explain (a bit more pedantically) how one actually finds "Developer:" in order to perform the requested command.

@drscotthawley
Copy link
Author

I'll submit a PR that includes instructions for "View > Command Pallette... > Developer: Running Extensions"

@gjsjohnmurray
Copy link
Contributor

Quite a lot of VS Code documentation assumes the user knows how to use Command Palette to execute commands. I think that is a reasonable assumption apart, obviously, from in the Getting Started stuff.

@drscotthawley
Copy link
Author

Closing now that PR#198 is merged.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants