Skip to content

Corrected hotkey for code comments on Mac #3901

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

Open
Lk-ux wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Corrected hotkey for code comments on Mac #3901

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 1-js/02-first-steps/02-structure/article.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ alert('World');
```

```smart header="Use hotkeys!"
In most editors, a line of code can be commented out by pressing the `key:Ctrl+/` hotkey for a single-line comment and something like `key:Ctrl+Shift+/` -- for multiline comments (select a piece of code and press the hotkey). For Mac, try `key:Cmd` instead of `key:Ctrl` and `key:Option` instead of `key:Shift`.
In most editors, a line of code can be commented out by pressing the `key:Ctrl+/` hotkey for a single-line comment and something like `key:Ctrl+Shift+/` -- for multiline comments (select a piece of code and press the hotkey). For Mac, try `key:Cmd+/` for single-line comments and `key:Option+Shift+A` (on VS Code) for multiline comments.
Copy link

Copilot AI Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The multiline comment hotkey documentation has inconsistencies:

  1. Editor specificity: Adding "(on VS Code)" only for multiline comments is inconsistent since the earlier part of the sentence refers to "most editors" without specifying which one. This creates confusion about whether the Mac instructions apply generally or only to VS Code.

  2. Key order: The standard convention is to list modifier keys in order (Shift before Option), so it should be key:Shift+Option+A rather than key:Option+Shift+A.

  3. Incomplete information: If you're going to specify VS Code for multiline comments, you should clarify what applies to other editors. Alternatively, provide the general Mac equivalent like the original approach, or note that multiline comment hotkeys vary by editor.

Consider revising to either:

  • Keep it general: "For Mac, try key:Cmd+/ for single-line comments and key:Cmd+Option+/ or key:Shift+Option+A for multiline comments (varies by editor)."
  • Or be consistent about editor-specificity throughout the sentence.
Suggested change
In most editors, a line of code can be commented out by pressing the `key:Ctrl+/` hotkey for a single-line comment and something like `key:Ctrl+Shift+/` -- for multiline comments (select a piece of code and press the hotkey). For Mac, try `key:Cmd+/` for single-line comments and `key:Option+Shift+A` (on VS Code) for multiline comments.
In most editors, a line of code can be commented out by pressing the `key:Ctrl+/` hotkey for a single-line comment and something like `key:Ctrl+Shift+/` for multiline comments (select a piece of code and press the hotkey). For Mac, try `key:Cmd+/` for single-line comments and `key:Cmd+Option+/` or `key:Shift+Option+A` for multiline comments (hotkeys may vary by editor).

Copilot uses AI. Check for mistakes.
```

````warn header="Nested comments are not supported!"
Expand Down