vladimir-vovk commented Aug 1, 2016 Yes, I had (setq which-function-mode t) in my .spacemacs file. A word for the moment when you realise technology has outpaced you What will you bring for Thanksgiving? Edit: It's worth noting that it's many variations on this message that are being displayed, so the function number (80427 in my example) changes on almost every line. I'll push a change, see if it fixes your problem. have a peek here
Already have an account? By default it is applied using jit-lock-mode, which applies it "lazily" (aka "just-in-time"), which has the disadvantage that it is applied at a time where we can't display message (or enter Thanks. Install adaptive-wrap.el from ELPA > > 2. https://github.com/milkypostman/powerline/issues/65
uh... Install sbcl or clisp or any CL supported by slime > > 1. I did this: .
Could the atmosphere be compressed and put into bottles? Set font-lock-support-mode to nil, then turn font-lock off and then back on. It's good, not bad, to have error msgs in *Messages*. (Just one opinion.) –Drew Aug 14 '15 at 18:06 Normally I would agree, but the problem is that my Should this happen, > the function signals the anomaly by returning `nil' instead. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The simplest fix seems to be for the fill prefix to default
It seems to me that in 24.2.92, the code is able to continue without waiting for animate-string to finish. Appearance of a boggart to someone who is most afraid of boggarts Living on an Isolated Peninsula - Making it Impossible to Leave A valentine's code more hot questions question feed Emacs -q -l t.el (t.el assumes sbcl, which you may want to change) > > 2. Any idea how to debug this problem? > Error during redisplay: (jit-lock-function 1) signaled (wrong-type-argument stringp nil) > Error during redisplay: (jit-lock-function 561) signaled (wrong-type-argument stringp nil) > Error during redisplay:
A single short compile can generate 50 of these, so the buffer quickly becomes filled with nothing else. –RealityMonster Aug 14 '15 at 19:50 1 The reason this "doesn't seem Reload to refresh your session. You signed out in another tab or window. What difficulty would the Roman Empire have besieging a fantasy kingdom's 49 m wall?
M-x load-file RET elpa/packages/adaptive-wrap/adaptive-wrap.el RET . https://lists.gnu.org/archive/html/emacs-devel/2013-01/msg00156.html can you show it? M-x adaptive-wrap-prefix-mode 2. (animate-string "hello" 0) So no need for slime or cl. Leo Eli Zaretskii Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ Re: How to debug Error during redisplay > From:
Also if I set inhibit-eval-during-redisplay to t, the error is gone as well. http://powerproxy.net/emacs-error/emacs-error-invalid-face.html Install adaptive-wrap.el from ELPA > 2. I did: > 1. If you're lucky, >> the same problem will occur, but this time it'll be in a context where >> debug-on-error works. > But I couldn't get it to work.
I've noticed some redundancy in how data structures are passed around, but I'm not sure I am smart enough to optimize it all. Sign up for free to join this Should this happen, the function signals the anomaly by returning `nil' instead. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Here's the backtrace: Breakpoint 3, wrong_type_argument (predicate=56455034, value=56403994) at data.c:99 You signed in with another tab or window. Check This Out Or does any use of > > animate-string trigger these messages? > > I mean the slime package, the same one running in 24.2 and 24.2.92.
The backtrace is below, I hope this will allow to fix adaptive-wrap. Error during redisplay: (jit-lock-function 1) signaled (wrong-type-argument stringp nil) Error during redisplay: (jit-lock-function 561) signaled (wrong-type-argument stringp nil) Error during redisplay: (jit-lock-function 1) signaled (wrong-type-argument stringp nil) [2 times] Leo reply Try to find out what is calling jit-lock-function and passing it a number instead of a string.
more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed M-x slime Thanks, so it sounds like the culprit might be adaptive-wrap, and not slime or animate-string. For example (progn (font-lock-add-keywords nil '( ;; ("hi1" . 'success) ("hi2" . (intern (concat "warn" "ing"))) )) (font-lock-fontify-buffer)) will produce the following message in Messages buffer: Error during redisplay: (jit-lock-function 1) should I do the report there?
Which code is that? It is amazing to me what @tkf was able to accomplish in elisp, but he sure loves to throw in the kitchen sink with his data structures, though I can't say But bt gives me this: -------------------------------- Lisp Backtrace: "redisplay_internal (C function)" (0x69d758) "redisplay" (0x5fbf58a0) "sit-for" (0x5fbf5f30) "animate-string" (0x5fbf6480) "if" (0x5fbf6990) "let" (0x5fbf6cd0) "progn" (0x5fbf6f30) "if" (0x5fbf7190) "slime-startup-message" (0x5fbf7428) "funcall" (0x5fbf7420) "slime-repl-update-banner" this contact form But I couldn't get it to work.
You signed out in another tab or window. Install sbcl or clisp or any CL supported by slime 1.