Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Consider making all top level bindings non-default #164
There's a few top level bindings in markdown-mode e.g.
These have annoyed me somewhat over the years, but I noticed people having issues with these bindings, so I think it's worth opening discussion at least.
While disabling some of these might cause problems for some existing users, a command or customizable setting to enable these top level bindings, could be provided.
Since markdown-mode otherwise does a fantastic job of keeping bindings on
That shouldn't really have relevance to Markdown mode. It's supposed to be a text markup format, not a wide reaching app like Org
That said, there are certainly a few top level org-mode bindings which are also obtrusive. But given that Org has such a broad scope it's not so straight forward to know where to draw the line.
Markdown isn't ambiguous in that way, so it's best to avoid trying to draw tenuous parallels.
Uniformity of the users chosen editing experience, and default and user defined top level bindings should be respected.
Sorry for the long delay in responding. Just a quick update...
When I added the keybindings in question, they were indeed inspired by Org mode. Until you opened this issue I didn't know that M-<left> and M-<right> were even bound (I've always used M-f and M-b). I'm closing in on a v2.3 stable release and after that I'm planning to add some new features which will involve re-thinking the existing keybindings anyway. So, I understand the concern and will either change the keybindings (e.g., by combining the functionality into other keys) or add a custom variable to enable/disable the toplevel keys.
The list/outline editing commands and the promotion/demotion commands have now been removed from the top-level positions. Previously they were at:
The commands have been consolidated so that they work on list or heading subtrees, depending on context, and are now bound under C-c: