Mac app should avoid OS defualt keymap

[windk]

As We know Ctrl + B is mapping as Back on System level.
I use Ctrl + B everywhere(Chrome location, command line, emacs, text editor and so on), but Macdown map Ctrl + B as block quote

Can I set My own keymap? Or Can macdown use another keymap?

[uranusjr]

You are absolutely correct. I am not sure what we must avoid (aside from ^B, which you already mentioned), but maybe we need to avoid all control-based shortcuts.

Current shortcuts that cause (or may cause) problems include:

• HTML entities insertion (ctrl-shift-7, ctrl-shift-period, ctrl-shift-comma, ctrl-shift-space, ctrl-shift-quote, and ctrl-quote)
• Unordered list (ctrl-U)
• Blockquote (ctrl-B)
• Link (ctrl-shift-L)
• Image (ctrl-shift-I)

Are there others? I don’t really have ideas of what system shortcuts (there are so many) we should avoid, and what we should assign them to instead. Do you (or anyone who is interested) have any suggestions?

Before this is sorted out, you can always modify/add shortcuts in the system keyboard preference pane.

[aaronraimist]

Not sure why Editor 1:1 Preview is OPT + CMD + 0, in Firefox it's just CMD + 0

[uranusjr]

Cmd-0 is already used to convert headers into normal paragraphs. I got the opt-cmd idea from Sublime Text’s Layout hotkeys (opt-cmd-1 for single-column, 2 to 4 for multi-column). But maybe 0 is not a good number for that. And we’ll need to tweak those at least a little bit after #49 is merged, I think.

[windk]

actually those keymap are similar to emacs keymap.

• Ctrl - A move caret to beginning of line
• Ctrl - E move caret to end of line
• Ctrl - F forword one character
• Ctrl - B back one character
• Ctrl - P previous line
• Ctrl - N next line
• Ctrl - K killing
• Ctrl - Y yank
• Ctrl - O new line after caret
• Ctrl - D delete one character

what about add a keymap layout feature, users can choose keymap layout like Vim, Emacs and so on, just like cmd markdown,

[uranusjr]

OS X offers native key-mapping, so unless we’re doing something that differs a lot from the system norm, building a app-specific feature is unnecessary. Unless we are doing something that the system’s built-in tools can’t, like what I proposed in #42, we don’t need to build our own wheels.

And as I said in #34, building Vim (or Emacs, FWIW) modes would require considerable work on the underlying editor structure. It’s not impossible, just not worth the effort for me. I’d be happy to merge it if someone takes the time to build the feature, but I’ll focus on other things first.