Open apc opened 3 years ago
I was able to reproduce this with emacs -Q
like so, with the current latest markdown-mode and smartparens:
emacs -Q -L src/markdown-mode -L src/smartparens -l markdown-mode -l smartparens-markdown /tmp/z.md --eval '(smartparens-mode)'
This bug seems to be able to cause bad effects across many intervening lines, too, e.g., typing **
at the end of this file also triggers the bug and the user may be much less likely to notice than when it is nearby:
`foo`
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
I can also reproduce this issue. Thanks for the report.
Expected behavior
I'm not quite sure what to expect here, since I realize it's not clear how best to interpret '*' at the beginning of a line. So either:
or
Actual behavior
Text goes from
to
after typing the second asterisk.
Steps to reproduce the problem
I have not, unfortunately, managed to reproduce this problem starting with
emacs -q
. So I'm looking for help understanding what function is being called upon typing one of the delimiters thatsmartparens
recognizes. (M-x view lossage
tells me that my second*
just calledself-insert-command
, so I guess the more fundamental problem is that I don't know how to ask the question I want, other than: what is happening when I type that second asterisk?)Backtraces if necessary (
M-x toggle-debug-on-error
)Environment & version information
In recent enough
smartparens
you can callM-x sp-describe-system
to generate this report. Please fill manually what we could not detect automatically. Edit the output as you see fit to protect your privacy.