File Mode Specification Error Void-variable C-emacs-features
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn update spacemacs more about Stack Overflow the company Business Learn more about hiring developers or posting company mode ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What does it mean when emacs tells me “File mode specification error”? up vote 14 down vote favorite 7 This is the most useless error message I have ever seen. I think it translates to .. "error". The full error message from the *Messages* buffer is: File mode specification error: (wrong-type-argument characterp "string value here") I think the latter part of that message means that emacs was expecting a character and got a string. But how do I go about diagnosing just what it means when emacs tells me "File mode specification error" ? and how do I narrow down where this error is originating? How are these two errors (file mode error, expecting character and got string) related? emacs share|improve this question edited Nov 15 '10 at 12:23 asked Nov 14 '10 at 22:39 Cheeso 115k61349569 2 A little more context about the conditions under which the error is triggered would help –Richard H Nov 14 '10 at 23:16 So, are you opening a file through find-file and at the end of opening the file Emacs reports this error? Or are you calling normal-mode yourself? What is the type of the file you are trying to open? –vpit3833 Nov 15 '10 at 1:51 @vpit3833, I'm not trying to open a file. not explicitly anyway. I'm running some elisp code, but ... even that doesn't open a file, not even implicitly. @Richard, I understand what you're asking, but I'm not seeking help in diagnosing this particular error. I'm seeking an explanation for this ver common emacs error message. It seems to pop up in many circumstances, often not (apparently) linked to opening a file at all. I'
Sign in Pricing Blog Support Search GitHub This repository Watch 452 Star 9,304 Fork 2,458 syl20bnr/spacemacs Code Issues 872 Pull requests 206 Projects 4 Wiki Pulse Graphs New issue Org-mode: File mode specification error: (void-function nil) #1593 Closed sooheon opened this Issue May 14, 2015 · 7 comments Projects None yet Labels Org To be reproduced Milestone No milestone Assignees No one assigned 4 participants http://stackoverflow.com/questions/4180111/what-does-it-mean-when-emacs-tells-me-file-mode-specification-error sooheon commented May 14, 2015 Upon opening an org file, I get the above error and evil-org-mode is not activated. It works if I call it manually. The org/init-evil-org use-package seems correct to me, but I'm not too sure. Owner syl20bnr commented May 17, 2015 On which branch are you ? syl20bnr https://github.com/syl20bnr/spacemacs/issues/1593 added Org to be confirmed labels May 17, 2015 sooheon commented May 17, 2015 I am on develop. Just tried with latest develop and nuking elpa again, problem persists for me. Owner syl20bnr commented May 18, 2015 What is your version of emacs ? Can you enable debugging with SPC t D before opening the org file and paste the callstack here? sooheon commented May 18, 2015 Version: GNU Emacs 24.5.1 (x86_64-apple-darwin13.4.0, NS apple-appkit-1265.21) of 2015-04-11 on builder10-9.porkrind.org Debugger output: Debugger entered--Lisp error: (void-function nil) nil() run-hooks(change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook) apply(run-hooks (change-major-mode-after-body-hook text-mode-hook outline-mode-hook org-mode-hook)) run-mode-hooks(org-mode-hook) org-mode() set-auto-mode-0(org-mode nil) set-auto-mode() normal-mode(t) after-find-file(nil t) find-file-noselect-1(#
date from a time when some character sets didn’t have all the characters that C needs, and are now utterly obsolete.) There is no way to apply auto newline http://www.gnu.org/s/emacs/manual/html_node/ccmode/Limitations-and-Known-Bugs.html settings (see Auto-newlines) on already typed lines. That’s only a feature to https://www.emacswiki.org/emacs/NxhtmlOldBugs ease interactive editing. To generalize this issue a bit: CC Mode is not intended to be used as a reformatter for old code in some more or less batch-like way. With the exception of some functions like c-indent-region, it’s only geared to be used interactively to edit file mode new code. There’s currently no intention to change this goal. If you want to reformat old code, you’re probably better off using some other tool instead, e.g., GNU indent in The ‘indent’ Manual, which has more powerful reformatting capabilities than CC Mode. The support for C++ templates (in angle brackets) is not yet complete. When a non-nested template is file mode specification used in a declaration, CC Mode indents it and font-locks it OK. Templates used in expressions, and nested templates do not fare so well. Sometimes a workaround is to refontify the expression after typing the closing ‘>’. In a k&r region (the part of an old-fashioned C function declaration which specifies the types of its parameters, coming between the parameter list and the opening brace), there should be at most 20 top-level parenthesis and bracket pairs. This limit has been imposed for performance reasons. If it is violated, the source file might be incorrectly indented or fontified. On loading CC Mode, sometimes this error message appears: File mode specification error: (void-variable c-font-lock-keywords-3) This is due to a bug in the function eval-after-load in some versions of (X)Emacs. It can manifest itself when there is a symbolic link in the path of the directory which contains (X)Emacs. As a workaround, put the following into your .emacs file, fairly early on: (defun my-load-cc-fonts () (require "cc-fonts")) (add-hook 'c-initialization-hook 'my-load-cc-fonts) Next: FAQ, Previous: Performance Issues, Up: Top [Contents][Index]
for new bugs, and don’t add any more to this page.Solved problems.nosearchWhen I put nxhtml folder into the site-lisp directory, a lot of non-lisp directories (such as doc/, img/ etc.) will be found in the load-path. How about adding “.nosearch” files to these directories? – SeijiZenitani I have added .nosearch to all those subdirs in version 1.04 - thanks for telling me again!nxml-whereI find nxml-where mode very useful. However I have two suggestions nxml-where-get-id-pattern should have the configurable attribute to look for. I’m currently editing WSDL files and I want to look for “name” attribute. I hacked this in. Perhaps a configurable variable?Inside nxml-where-update-once the (run-with-idle-timer 0 …) make continuous movement very jerky. I use (run-with-idle-timer 0.6 for smoother operation. Perhaps another config variable? 😊– AadityaSood I believe this as least partly is solved in version 1.04Turning on by magic-mode-alistNxhtmlMode by default is triggered on non-XML HTML files also, and I don’t like that fact very much. So I used magic-mode-alist to activate NxhtmlMode on files that feel like XHTML only: (add-to-list 'magic-mode-alist '("<\\?xml \\(?:.\\|
\\)+?>\\(?:\\|
\\) and
© Copyright 2019|winbytes.org.