Error During Redisplay Wrong-type-argument Stringp Nil
+0800 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (OS X 10.8.2) I have just noticed this (using 24.2.92) in the *message* buffer which I cannot reproduce in emacs 24.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: (jit-lock-function 1) signaled (wrong-type-argument stringp nil) [2 times] Leo reply via email to [Prev in Thread] Current Thread [Next in Thread] How to debug Error during redisplay, Leo Liu<= Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/11 Re: How to debug Error during redisplay, Leo Liu, 2013/01/11 Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/11 Re: How to debug Error during redisplay, Leo Liu, 2013/01/12 Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12 Re: How to debug Error during redisplay, Leo Liu, 2013/01/12 Re: How to debug Error during redisplay, Leo Liu, 2013/01/12 Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12 Re: How to debug Error during redisplay, Leo Liu, 2013/01/12 Re: How to debug Error during redisplay, Eli Zaretskii, 2013/01/12 Prev by Date: Re: RFE: require and load-path-shadowing Next by Date: Re: File watch support in autorevert.el Previous by thread: Re: Emacs Mac port Next by thread: Re: How to debug Error during redisplay Index(es): Date Thread
Sign in Pricing Blog Support Search GitHub This repository Watch 451 Star 9,220 Fork 2,427 syl20bnr/spacemacs Code Issues 863 Pull requests 204 Projects 4 Wiki Pulse Graphs New issue Wrong type argument: stringp, nil #3652 Open sumyuga opened this Issue Nov 3, 2015 · 24 comments Projects None yet Labels - Forum - Docker Documentation ✏ FAQ Hacktoberfest Ready for work Milestone No milestone Assignees No one assigned 9 participants sumyuga commented Nov 3, 2015 My host system is OS X and docker with Debian used to development. I have emacs 24.4.1 on Debian installed. After emacs starts I get this: Warning (initialization): An error occurred https://lists.gnu.org/archive/html/emacs-devel/2013-01/msg00156.html while loading '/root/.emacs.d/init.el' Wrong type argument: stringp, nil As a result it's not working powerline with key bindings But on my host system is all great. Collaborator TheBB commented Nov 3, 2015 Do --debug-init to see where the error comes from. sumyuga commented Nov 3, 2015 after this command starts emacs shows "Entering debugger..." and it is frozen – no any reaction Owner syl20bnr commented Nov 3, 2015 Is it with a vanilla https://github.com/syl20bnr/spacemacs/issues/3652 .spacemacs ? sumyuga commented Nov 3, 2015 Of course. I have copied from template file ~/.emacs.d/core/templates/.spacemacs.template Collaborator TheBB commented Nov 4, 2015 You can work around this error by opening .emacs.d/elpa/archives/melpa/archive-contents and deleting the nil at the end of the list. I'm not sure why that happens in the first place. sumyuga commented Nov 4, 2015 No, it doesn't work StreakyCobra added to be reproduced <=(- UBO -)=> labels Nov 6, 2015 autosquid commented Jan 5, 2016 It looks like the same thing happened to me, and solution from @TheBB works. StreakyCobra added Fixed in develop Fixed in current release-x.x and removed Fixed in develop labels Jan 5, 2016 StreakyCobra commented Jan 5, 2016 @TheBB has documented this problem in the FAQ autosquid commented Jan 6, 2016 @StreakyCobra In my case, delete the elpa and re-download did not solve the problem, but by opening .emacs.d/elpa/archives/melpa/archive-contents and deleting the nil at the end of the list works. syl20bnr removed the Fixed in current release-x.x label Jan 7, 2016 sumyuga commented Jan 29, 2016 It's still not working for me. Guys, give a solution please. StreakyCobra commented Jan 29, 2016 Let me check if I have some ready-to-use solutions under my pillow… Nope, doesn't seem so. If you want more help you will have to give us more inf
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 http://emacs.stackexchange.com/questions/14754/is-there-a-way-to-suppress-errors-in-the-messages-buffer Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Emacs Questions Tags Users Badges Unanswered Ask Question _ Emacs Stack Exchange is a question and answer site for those using, extending or developing Emacs. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best error during answers are voted up and rise to the top Is there a way to suppress errors in the *Messages* buffer? up vote 0 down vote favorite I have a persistent problem with some jit-lock-function somewhere whenever I compile. I'm actually invoking the visual studio compiler, and I assume some of the output is somehow abhorrent to emacs. I updated to a newer version of emacs error during redisplay today because I found that there was an error in cc-fonts.el that would cause trouble, but even with that fix I still see this: Error during redisplay: (jit-lock-function 80427) signaled (wrong-type-argument stringp nil) It doesn't seem to be causing any trouble, and it's not worth any more of my time to fix it. Can I get the messages buffer to stop showing it to me? 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. That means I end up with hundreds of these messages filling up my messages buffer, pushing out any meaningful information. font-lock message share|improve this question edited Aug 14 '15 at 19:51 asked Aug 14 '15 at 15:54 RealityMonster 1685 1 My advice is to just ignore it. 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 messages buffer is absolutely filled with these messages, and it's hard to see anything that's ACTUALLY worth paying attention to. A single sho