Hmm. Those both appear to work using the browserstack emulator (I’m not 100% about the ”.0.3325″ part of the version number but just tried on chome 65 for both Sierra and High Sierra. Which OS are you on? Also doublechecking that you’re in the rich text editor? The markdown one is not expected to work)
Yeah – in principle probably it can work but it gets much more complicated (trying to integrate markdown with LaTeX is one of the things that resulted in extremely long wordcounts).
Ah, in that case this looks like an issue where it’s just hard to account for every browser’s hotkeys (we had gone through a few other plausible hotkeys for LaTeX that were in use by chrome). So in this case ctrl-cmd-M works because it’s an override over Safari’s hotkeys.
We could list this particular issue/solution in the helper-text, but I’m not sure it’s practical as a general policy to account for all possible browser hotkey overrides.
Hmm. Those both appear to work using the browserstack emulator (I’m not 100% about the ”.0.3325″ part of the version number but just tried on chome 65 for both Sierra and High Sierra. Which OS are you on? Also doublechecking that you’re in the rich text editor? The markdown one is not expected to work)
Oh! Well, never mind, then.
Yeah – in principle probably it can work but it gets much more complicated (trying to integrate markdown with LaTeX is one of the things that resulted in extremely long wordcounts).
Mine was in the text editor. Even in the text editor, Cmd 4 sends me to my 4th tab in the window, instead of entering latex.
Ah, in that case this looks like an issue where it’s just hard to account for every browser’s hotkeys (we had gone through a few other plausible hotkeys for LaTeX that were in use by chrome). So in this case ctrl-cmd-M works because it’s an override over Safari’s hotkeys.
We could list this particular issue/solution in the helper-text, but I’m not sure it’s practical as a general policy to account for all possible browser hotkey overrides.