[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Error when editing C code
From: |
T.V Raman |
Subject: |
Error when editing C code |
Date: |
Wed, 15 Jun 2022 12:59:39 -0700 |
Appears to be due to incorrect loading of macros in cc-mode.
If I try editing a c/c++ file, I get this backtrace.
This emacs from Git @HEAD, I even did a make distclean followed by a
rebuild but the error persists.
Debugger entered--Lisp error: (void-function c-with-string-fences)
(c-with-string-fences nil nil nil nil t nil nil t (c-depropertize-new-text
c-after-change-escape-NL-in-string c-after-change-unmark-ml-strings
c-parse-quotes-after-change c-after-change-mark-abnormal-strings
c-extend-font-lock-region-for-macros c-neutralize-syntax-in-CPP
c-restore-<>-properties c-change-expand-fl-region))
(c-after-change 2617 2617 6)
(delete-and-extract-region 2617 2623)
(#f(compiled-function (beg end delete) #<bytecode -0xb2965821e55dad>) 2617
2623 delete)
(apply #f(compiled-function (beg end delete) #<bytecode -0xb2965821e55dad>)
(2617 2623 delete))
(#f(compiled-function (funs global args) #<bytecode -0x508bbc66466722>) nil
nil (2617 2623 delete))
(buffer-substring--filter 2617 2623 delete)
(filter-buffer-substring 2617 2623 delete)
(#f(compiled-function (beg end &optional region) "Kill (\"cut\") text between
point and mark.\nThis deletes the text from the buffer and saves it in the kill
ring.\nThe command \\[yank] can retrieve it from there.\n(If you want to save
the region without killing it, use \\[kill-ring-save].)\n\nIf you want to
append the killed region to the last killed text,\nuse \\[append-next-kill]
before \\[kill-region].\n\nAny command that calls this function is a \"kill
command\".\nIf the previous command was also a kill command,\nthe text killed
this time appends to the text killed last time\nto make one entry in the kill
ring.\n\nThe killed text is filtered by `filter-buffer-substring' before it
is\nsaved in the kill ring, so the actual saved text might be different\nfrom
what was killed.\n\nIf the buffer is read-only, Emacs will beep and refrain
from deleting\nthe text, but put the text in the kill ring anyway. This means
that\nyou can use the killing commands to copy text from a read-only
buffer.\n\nLisp programs should use this function for killing text.\n (To
delete text, use `delete-region'.)\nSupply two arguments, character positions
BEG and END indicating the\n stretch of text to be killed. If the optional
argument REGION is\n non-nil, the function ignores BEG and END, and kills the
current\n region instead. Interactively, REGION is always non-nil, and so\n
this command always kills the current region." (interactive
#f(compiled-function () #<bytecode -0x1aacdb1bd27856fc>)) #<bytecode
-0x436d732fd395672>) 2617 2623 nil)
(ad-Advice-kill-region #f(compiled-function (beg end &optional region) "Kill
(\"cut\") text between point and mark.\nThis deletes the text from the buffer
and saves it in the kill ring.\nThe command \\[yank] can retrieve it from
there.\n(If you want to save the region without killing it, use
\\[kill-ring-save].)\n\nIf you want to append the killed region to the last
killed text,\nuse \\[append-next-kill] before \\[kill-region].\n\nAny command
that calls this function is a \"kill command\".\nIf the previous command was
also a kill command,\nthe text killed this time appends to the text killed last
time\nto make one entry in the kill ring.\n\nThe killed text is filtered by
`filter-buffer-substring' before it is\nsaved in the kill ring, so the actual
saved text might be different\nfrom what was killed.\n\nIf the buffer is
read-only, Emacs will beep and refrain from deleting\nthe text, but put the
text in the kill ring anyway. This means that\nyou can use the killing
commands to copy text from a read-only buffer.\n\nLisp programs should use this
function for killing text.\n (To delete text, use `delete-region'.)\nSupply two
arguments, character positions BEG and END indicating the\n stretch of text to
be killed. If the optional argument REGION is\n non-nil, the function ignores
BEG and END, and kills the current\n region instead. Interactively, REGION is
always non-nil, and so\n this command always kills the current region."
(interactive #f(compiled-function () #<bytecode -0x1aacdb1bd27856fc>))
#<bytecode -0x436d732fd395672>) 2617 2623)
(apply ad-Advice-kill-region #f(compiled-function (beg end &optional region)
"Kill (\"cut\") text between point and mark.\nThis deletes the text from the
buffer and saves it in the kill ring.\nThe command \\[yank] can retrieve it
from there.\n(If you want to save the region without killing it, use
\\[kill-ring-save].)\n\nIf you want to append the killed region to the last
killed text,\nuse \\[append-next-kill] before \\[kill-region].\n\nAny command
that calls this function is a \"kill command\".\nIf the previous command was
also a kill command,\nthe text killed this time appends to the text killed last
time\nto make one entry in the kill ring.\n\nThe killed text is filtered by
`filter-buffer-substring' before it is\nsaved in the kill ring, so the actual
saved text might be different\nfrom what was killed.\n\nIf the buffer is
read-only, Emacs will beep and refrain from deleting\nthe text, but put the
text in the kill ring anyway. This means that\nyou can use the killing
commands to copy text from a read-only buffer.\n\nLisp programs should use this
function for killing text.\n (To delete text, use `delete-region'.)\nSupply two
arguments, character positions BEG and END indicating the\n stretch of text to
be killed. If the optional argument REGION is\n non-nil, the function ignores
BEG and END, and kills the current\n region instead. Interactively, REGION is
always non-nil, and so\n this command always kills the current region."
(interactive #f(compiled-function () #<bytecode -0x1aacdb1bd27856fc>))
#<bytecode -0x436d732fd395672>) (2617 2623))
(kill-region 2617 2623)
(#f(compiled-function (arg) "Kill characters forward until encountering the
end of a word.\nWith argument ARG, do this that many times." (interactive "p")
#<bytecode -0xe1aa8af62fe5343>) 1)
(ad-Advice-kill-word #f(compiled-function (arg) "Kill characters forward
until encountering the end of a word.\nWith argument ARG, do this that many
times." (interactive "p") #<bytecode -0xe1aa8af62fe5343>) 1)
(apply ad-Advice-kill-word #f(compiled-function (arg) "Kill characters
forward until encountering the end of a word.\nWith argument ARG, do this that
many times." (interactive "p") #<bytecode -0xe1aa8af62fe5343>) 1)
(kill-word 1)
(#<subr funcall-interactively> kill-word 1)
(apply #<subr funcall-interactively> kill-word 1)
(ad-Advice-funcall-interactively #<subr funcall-interactively> kill-word 1)
(apply ad-Advice-funcall-interactively #<subr funcall-interactively>
(kill-word 1))
(funcall-interactively kill-word 1)
(#<subr call-interactively> kill-word nil nil)
(apply #<subr call-interactively> kill-word (nil nil))
(call-interactively@ido-cr+-record-current-command #<subr call-interactively>
kill-word nil nil)
(apply call-interactively@ido-cr+-record-current-command #<subr
call-interactively> (kill-word nil nil))
(call-interactively kill-word nil nil)
(command-execute kill-word)
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
?7?4 Id: kg:/m/0285kf1 ?0?8
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
??? Id: kg:/m/0285kf1 ????
- Error when editing C code,
T.V Raman <=