I haven't yet been able to consistently reproduce this issue, so I'll update the steps to reproducing it when I figure out how, but this bug happens most in prolonged editing sessions (like an hour long), where the user is quickly creating blocks, committing them, etc.
Unexpected BehaviorBasically, when the user tries to markdown-edit-code-block within valid code fence, they get the error
Wrong type argument: integer-or-marker-p, nil
markdown-edit-code-block works normally
As I said before, I haven't been able to reproduce the bug yet, but it generally occurs in long editor sessions. I'll update this section as soon as I can get this issue reproducing.
Backtrace
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
markdown-edit-code-block()
debugger-may-continue = t
inhibit-redisplay = nil
inhibit-debugger = t
inhibit-changing-match-data = nil
funcall-interactively(markdown-edit-code-block)
[no locals]
call-interactively(markdown-edit-code-block nil nil)
[no locals]
command-execute(markdown-edit-code-block)
[no locals]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4