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
Versions: Emacs (latest emacs-26 branch build as of today), Nim compiler (Nim Compiler Version 0.17.3 (2017-11-15), git hash: 39c304f8822b350472d584f72ca8f220bde20f7f), and nimsuggest (same as nim).
Are you using latest version of nim-mode? Yes
Are there message related to nim-mode in *Messages* buffer? N/A
Did you read README.md? Yes
Is your problem related to nimsuggest-mode? (company-mode, flycheck, or el-doc) No
And describe your problem:
Use of visual-line-move in nim-mode exposed an emacs bug and causes crashes when doing org-comment-dwim in a nim SRC_BLOCK in an Org file (debbugs # 29326).
The Lisp backtrace explains the interaction between org-mode and nim-mode:
While the emacs bug was clearly present (and later fixed in emacs-26/90add182), Eli had these comments:
The trigger was the call to line-move-visual in nim-mode. So you need
to do something that causes that function to be called by nim-mode,
when Org does the indent thing. I think this doesn't happen
frequently because most modes used in source snippets in Org buffers
don't call line-move-visual (why would they? that function is for
interactively moving cursor vertically).
The text was updated successfully, but these errors were encountered:
Thank you for conforming the bug. I'm assuming line-move function calls the line-move-visual function in nim-mode and I think it could be changed line-move-1 instead. I'll check when I have time. (indent stuff is kinda vulnerable part in nim-mode and may take some time to fix indentation test)
Conforming Bugs
Please tell us below:
nim
).*Messages*
buffer? N/AAnd describe your problem:
Use of
visual-line-move
innim-mode
exposed an emacs bug and causes crashes when doingorg-comment-dwim
in anim
SRC_BLOCK in an Org file (debbugs # 29326).The Lisp backtrace explains the interaction between
org-mode
andnim-mode
:While the emacs bug was clearly present (and later fixed in emacs-26/90add182), Eli had these comments:
The text was updated successfully, but these errors were encountered: