You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suppose I am editing a comment in a latex file, e.g.,
Blah blah
% here is a comment (|)
blah blah
where point is at (|).
If I strike ", I expect the insertion of a plain ", or perhaps a pair like either "(|)" or like ``(|)''
Actual behavior
Instead, I get this
Blah blah
% here is a comment`(|)'''
blah blah
Steps to reproduce the problem
Install smartparens
Configure with (require 'smartparens-config)
Open a LaTeX file
Activate smartparens: (smartparens-mode)
Put cursor in a commented line (one that starts with %)
Strike "
Backtraces if necessary (M-x toggle-debug-on-error)
Environment & version information
I first noticed this in spacemacs, but I reproduced this in Vanilla emacs with only smartparens installed (using straight installed commit 3ed34cb). This issue appears whether I use LaTeX-mode as provided by auctex, or just the latex-mode that ships with emacs.
Expected behavior
Suppose I am editing a comment in a latex file, e.g.,
Blah blah % here is a comment (|) blah blah
where point is at
(|)
.If I strike
"
, I expect the insertion of a plain"
, or perhaps a pair like either"(|)"
or like``(|)''
Actual behavior
Instead, I get this
Blah blah % here is a comment`(|)''' blah blah
Steps to reproduce the problem
(require 'smartparens-config)
(smartparens-mode)
%
)"
Backtraces if necessary (
M-x toggle-debug-on-error
)Environment & version information
I first noticed this in
spacemacs
, but I reproduced this in Vanilla emacs with only smartparens installed (using straight installed commit 3ed34cb). This issue appears whether I use LaTeX-mode as provided by auctex, or just the latex-mode that ships with emacs.smartparens
version:M-x emacs-version
): 29.1Commentary
I'm not sure what's going all batty, but I suspect this could be fixed by adding
sp-in-comment-p
hereThe text was updated successfully, but these errors were encountered: