Debugger Entered-lisp Error Void-function Eruby-nxhtml-mumamo
Sign in Pricing Blog Support Search GitHub This repository Watch 215 Star 3,143 Fork 1,389 bbatsov/prelude Code Issues 133 Pull requests 10 Projects 0 Wiki Pulse Graphs New issue Debugger entered--Lisp error: (void-function filename) #307 Closed pigmej opened this Issue Apr 25, 2013 · 8 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 6 participants pigmej commented Apr 25, 2013 Debugger entered--Lisp error: (void-function filename) filename("/home/pigmej/.emacs.d/elpa/flycheck-20130424.2259/flycheck.elc") flycheck--declare-checker-1(bash "A Bash syntax checker using the bash executable.\n\nSee URL `http://www.gnu.org/software/bash/'." :command ("bash" "--norc" "-n" "--" source) :error-patterns (("^\\(?1:.+\\):[^0-9]+\\(?2:[0-9]+\\) *: *\\(?4:.*\\)$" error)) :modes sh-mode :predicate (eq sh-shell (quote bash))) byte-code("\300\301\302\303\304\305\306\307\310\311\312&\n\210\313\314\315\316#\207" [flycheck--declare-checker-1 bash "A Bash syntax checker using the bash executable.\n\nSee URL `http://www.gnu.org/software/bash/'." :command ("bash" "--norc" "-n" "--" source) :error-patterns (("^\\(?1:.+\\):[^0-9]+\\(?2:[0-9]+\\) *: *\\(?4:.*\\)$" error)) :modes sh-mode :predicate (eq sh-shell (quote bash)) put coffee-coffeelint :flycheck-config-file-var flycheck-coffeelintrc] 11) (global-flycheck-mode 1) (if (fboundp (quote global-flycheck-mode)) (global-flycheck-mode 1) (add-hook (quote prog-mode-hook) (quote flycheck-mode))) eval-buffer(#
Example with Decrementing Counter, for a discussion.) However, your function definition has a bug. You have mistyped ‘1=’ for ‘1-’. Here is the broken definition: (defun triangle-bugged (number) "Return sum of numbers 1 through NUMBER inclusive." (let ((total 0)) (while (> number 0) (setq total (+ total number)) (setq number (1= number))) ; Error here. total)) If you are reading this in Info, you can evaluate this definition in the normal fashion. You will see triangle-bugged appear in the echo area. Now evaluate the triangle-bugged function with an argument of 4: (triangle-bugged 4) In a recent GNU Emacs, you will create and https://github.com/bbatsov/prelude/issues/307 enter a *Backtrace* buffer that says: ---------- Buffer: *Backtrace* ---------- Debugger entered--Lisp error: (void-function 1=) (1= number) (setq number (1= number)) (while (> number 0) (setq total (+ total number)) (setq number (1= number))) (let ((total 0)) (while (> number 0) (setq total ...) (setq number ...)) total) triangle-bugged(4) eval((triangle-bugged 4)) eval-last-sexp-1(nil) eval-last-sexp(nil) call-interactively(eval-last-sexp) ---------- Buffer: *Backtrace* ---------- (I have reformatted this example slightly; the debugger does not fold https://www.gnu.org/software/emacs/manual/html_node/eintr/debug.html long lines. As usual, you can quit the debugger by typing q in the *Backtrace* buffer.) In practice, for a bug as simple as this, the Lisp error line will tell you what you need to know to correct the definition. The function 1= is void. However, suppose you are not quite certain what is going on? You can read the complete backtrace. In this case, you need to run a recent GNU Emacs, which automatically starts the debugger that puts you in the *Backtrace* buffer; or else, you need to start the debugger manually as described below. Read the *Backtrace* buffer from the bottom up; it tells you what Emacs did that led to the error. Emacs made an interactive call to C-x C-e (eval-last-sexp), which led to the evaluation of the triangle-bugged expression. Each line above tells you what the Lisp interpreter evaluated next. The third line from the top of the buffer is (setq number (1= number)) Emacs tried to evaluate this expression; in order to do so, it tried to evaluate the inner expression shown on the second line from the top: (1= number) This is where the error occurred; as the top line says: Debugger entered--Lisp error: (void-function 1=) You can
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 https://www.emacswiki.org/emacs/NxhtmlOldBugs the load-path. How about adding “.nosearch” files to these directories? – SeijiZenitani I https://bugs.launchpad.net/bugs/557700 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 debugger entered-lisp 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 debugger entered-lisp error only: (add-to-list 'magic-mode-alist '("<\\?xml \\(?:.\\|
\\)+?>\\(?:\\|
\\) and
© Copyright 2019|winbytes.org.