From: "T.V Raman" <raman@google.com>
To: emacs-devel@gnu.org
Subject: Error when editing C code
Date: Wed, 15 Jun 2022 12:59:39 -0700 [thread overview]
Message-ID: <p91mtedaeac.fsf@google.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 7334 bytes --]
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 ð¦®
next reply other threads:[~2022-06-15 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 19:59 T.V Raman [this message]
2022-06-15 20:17 ` Error when editing C code Andreas Schwab
2022-06-15 20:29 ` T.V Raman
2022-06-15 21:24 ` T.V Raman
2022-06-16 5:10 ` Eli Zaretskii
2022-06-16 9:38 ` Alan Mackenzie
2022-06-16 13:52 ` T.V Raman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p91mtedaeac.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).