mdx-js / mdx-analyzer

MDX extension for Visual Studio Code

Home Page:https://marketplace.visualstudio.com/items?itemName=unifiedjs.vscode-mdx

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Keyboard shortcuts conflict with VS Code shortcuts

rdebeasi opened this issue · comments

Initial checklist

Affected packages and versions

MDX for Visual Studio Code v1.8.2

Steps to reproduce

  1. Open Visual Studio Code.
  2. Confirm that MDX for Visual Studio Code is installed.
  3. Open a Markdown file.
  4. Press Cmd+B (or ctrl+B).

More info on this keyboard shortcut:

Expected behavior

Sidebar toggles.

Actual behavior

Sidebar does not toggle.

To confirm that the MDX plugin's keyboard shortcut is taking precedence:

  1. Press Cmd+P (or Control+P) and choose "Preferences: Open Keyboard Shortcuts"
  2. In the "type to search" field, type "Cmd+B" (or "ctrl+B").
  3. Note that MDX "toggle strong" keyboard shortcut has taken precedence over VS Code's "Toggle Primary Side Bar Visibility" keyboard shortcut.

Would it be possible to choose a default shortcut that does not overlap with existing VS Code shortcuts? Thank you!

OS

macOS

Build and bundle tools

Other (please specify in steps to reproduce)

Welcome @rdebeasi! 👋
A counter point. Markdown is a document language.
Pretty much every document editor uses ctrl + b for bold/strong text.

As a default, ctrl + b for bold feels reasonable, it's what every other editor does, choosing something different would be unexpected to most users.
Though you are welcome to re-bind on your personal editor it if you feel that fast access to the sidebar is more of a priority to your document editing experience.

The rationale is indeed as @ChristianMurphy describes. Also Markdown All in One has the same behaviour.

I do understand your point, but I don’t think it’s generally better to use a different default shortcut. If you want to use Ctrl + B for toggling the side bar, you can use a custom key mapping.

I do notice just now that the toggle commands are broken, which I will look into.

Makes sense - thanks for explaining the thinking there! I'll go ahead and close this issue.

Hi! This was closed. Team: If this was fixed, please add phase/solved. Otherwise, please add one of the no/* labels.

Hi team! Could you describe why this has been marked as wontfix?

Thanks,
— bb