Error During Redisplay Wrong-type-argument Numberp Nil
Sign in Pricing Blog Support Search GitHub This repository Watch 39 Star 460 Fork 40 politza/pdf-tools Code Issues 55 Pull requests 7 Projects 0 Pulse Graphs New issue How to save/open password encrypted pdf files? #197 Open LukeSwart opened this Issue Apr 1, 2016 · 2 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants LukeSwart commented Apr 1, 2016 First, I want to say thanks so much for this package! It has really improved my experience when viewing pdf files. There doesn't seem to be any support for password-protected files. It seems that Gmail has support for this as well as the Adobe's tools, so I don't think the protocol is proprietary. Although I wouldn't be surprised if it was :-P When trying to open such a file, we get the following messages: File mode specification error: (error "epdfinfo: Error opening /home/me/Downloads/my-password-protected-file.pdf:Document is encrypted") pdf-info-query: epdfinfo: Error opening /home/me/Downloads/my-password-protected-file.pdf:Document is encryptedError during redisplay: (eval (number-to-string (pdf-view-current-page))) signaled (wrong-type-argument numberp nil) Error during redisplay: (eval (number-to-string (pdf-cache-number-of-pages))) signaled (error "epdfinfo: Error opening /home/me/Downloads/my-password-protected-file.pdf:Document is encrypted") I think this feature would be very nice to have, especially when someone sends you a password-protected file. I'm not exactly sure how to implement it though - any tips to get started would be great! LukeSwart commented Apr 1, 2016 It looks like there are numerous commandline tools that can do this here: http://www.cyberciti.biz/faq/removing-password-from-pdf-on-linux/ I'm not sure what dependencies we can expect to be installed, but if one of these is already bundled with this package, then we can just prompt the user to enter their password and trigger the appropriate command from there. Or perhaps there is a Lisp package that can be used for the encryption/decription instead... Owner politza commented Apr 2, 2016 If you look at the function pdf-info-open, you'll see, that it already has a password argument. Though I've never tested it. The error you mentioned could be caught and, if appropria
Sign in Pricing Blog Support Search GitHub This repository Watch 3 Star 32 Fork 5 abo-abo/swiper-helm Code Issues 0 Pull requests 0 Projects 0 Pulse Graphs New issue wrong-type-argument error when using swiper-helm #11 Closed iswanz opened this Issue Aug 10, 2016 · 9 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 3 participants iswanz commented Aug 10, 2016 My beloved swiper-helm has stopped working since https://github.com/politza/pdf-tools/issues/197 a recent update. Swiper works fine. I get the error: Error during redisplay: (eval (helm-show-candidate-number (car-safe helm-mode-line-string))) signaled (wrong-type-argument integer-or-marker-p nil) The swiper-helm buffer narrows as a I type, but when I try and move the selection (using any of the arrow keys) it jumps to the bottom of the swiper-helm buffer and then won't move. https://github.com/abo-abo/swiper-helm/issues/11 Some debug information: In GNU Emacs 25.1.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 2016-08-10 built on Repository revision: e13c5467fc0c08c6875653df56b8b54185d0c4cc Windowing system distributor 'The X.Org Foundation', version 11.0.11803000 System Description: Ubuntu 16.04.1 LTS Recent messages: Debug (ox-odt): No OpenDocument schema files installed [yas] Reloaded everything (snippets will load just-in-time).... Init file processed completely For information about GNU Emacs and the GNU system, type C-h C-a. Starting new Ispell process /usr/bin/aspell with default dictionary... Symbolic link to Git-controlled source file; follow link? (y or n) y Making helm-display-function local to swiper while let-bound! Error during redisplay: (eval (helm-show-candidate-number (car-safe helm-mode-line-string))) signaled (wrong-type-argument integer-or-marker-p nil) Mark set Thanks for your help! iswanz changed the title from Error when using swiper-helm to wrong-type-argument error when using swiper-helm Aug 10, 2016 Owner abo-abo commented Aug 10, 2016 swiper-helm hasn't been updated for months. I just checked with helm-20160808.2223 and Emacs 25, swiper-helm still works fine: narrowing works and the arrow keys work. Error during redisplay: (eval (helm-show-candidate-number (car-safe helm-mode-line-string))) signaled (wrong-type-argument inte
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 more http://stackoverflow.com/questions/18569410/how-to-debug-font-lock-keywords-error about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow http://emacs.stackexchange.com/questions/7178/cant-get-grep-search-in-helm-projectile-working is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up how to debug font lock keywords error up vote 2 down vote favorite error during How can I debug font lock keywords I write? 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) signaled (wrong-type-argument stringp 22) In order to see the call stack upon wrong-type-argument error, I invoke toggle-debug-on-error and Emacs still doesn't enter debugger upon font lock error. debugging emacs error during redisplay elisp syntax-highlighting font-lock share|improve this question asked Sep 2 '13 at 9:08 Jisang Yoo 1,661712 As to why we get an error for that particular example, stackoverflow.com/questions/18570224/… –Jisang Yoo Sep 2 '13 at 15:00 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted font-lock can be applied in different ways. 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 the debugger) because that would make us inf-loop. So there are two ways to work around the problem: Use jit-lock-debug-mode (recently added to Emacs's development code). Set font-lock-support-mode to nil, then turn font-lock off and then back on. Both options should change font-lock so that it is applied at a time where debugging can be used. share|improve this answer edited Sep 2 '13 at 14:23 answered Sep 2 '13 at 14:15 Stefan 19.7k12049 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your
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 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 answers are voted up and rise to the top Can't get grep search in helm-projectile working? up vote 1 down vote favorite I got thankfully introduced to use helm and helm-projectile for all the goodies it has and especially the helm-projectile-grep-search. I must say, this supercharged Emacs by a long shot. I learned that from this great tutorial : http://tuhdo.github.io/helm-projectile.html. Unfortunately, everyhting else was fine except grep search-related commands, they throwed this error by invoking them on my machine: Error during redisplay: (eval (helm-show-candidate-number (car-safe helm-mode-line-string))) signaled (wrong-type-argument integer-or-marker-p nil) [6 times] Error running timer helm-projectile-grep-or-ack: (wrong-type-argument stringp nil) The same error was issued when I used C-s or C-u C-s recursive grep search while in helm-find-files bound to C-x C-f. I run this on marked files with C-SPC. But rgrep works well which is built in Emacs (see image below). So I don't know what am I missing to get grep search work. Notes Machine: Windows 7 32bit. Emacs 24.4 Helm/Projectile/Helm-projectile all updated from MELPA. I have installed Cygwin and added to Path: helm microsoft-windows projectile share|improve this question edited Jan 9 '15 at 11:56 asked Jan 8 '15 at 17:14 doctorate 693115 rgrep used the built-in grep (written in Elisp) while helm-projectile-grep needs the external grep. If you don't like Cygwin, probably you should look at Mingw-w64, install it and set $PATH point to its binary directory. –Tu Do Jan 8 '15 at 18:09 @TuDo still