First off, let me say that I love minimap-mode and it's very helpful to me! It was exactly what I'm looking for and it works perfectly except in one case:
The customize group setting for minimap-mode is set so that it starts minimap-mode for the prog-mode major modes.
Then if I open a document in poly-markdown-mode, and move the cursor into an R code chunk, the minimap opens (so far so good) but Emacs freezes.
I can un-freeze it by pressing C-g three times in a row, and then it unfreezes long enough for me to get 1 keystroke in before it freezes again. So, I can move the cursor out of the R code chunk and into the regular markdown part of the document and then kill the buffer to save myself.
But I'd rather have a way to either get minimap-mode working properly in poly-markdown-mode, or a way to stop it from opening at all in poly-markdown-mode.
First off, let me say that I love minimap-mode and it's very helpful to me! It was exactly what I'm looking for and it works perfectly except in one case:
The customize group setting for minimap-mode is set so that it starts minimap-mode for the prog-mode major modes.
Then if I open a document in poly-markdown-mode, and move the cursor into an R code chunk, the minimap opens (so far so good) but Emacs freezes.
I can un-freeze it by pressing C-g three times in a row, and then it unfreezes long enough for me to get 1 keystroke in before it freezes again. So, I can move the cursor out of the R code chunk and into the regular markdown part of the document and then kill the buffer to save myself.
But I'd rather have a way to either get minimap-mode working properly in poly-markdown-mode, or a way to stop it from opening at all in poly-markdown-mode.
Do you have suggestions for a work-around?
Or failing that, could I request a bug fix?
Thanks so much!