Timeline for How to give my emacs access to ghostscript?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2016 at 17:34 | vote | accept | myotis | ||
| May 10, 2016 at 17:20 | comment | added | myotis | I have tried both exec-path and load-path, but none of them made gsview32 active. my path were C:\Program Files (x86)\emacs\emacs25093\bin C:\Program Files (x86)\gs\gs9.09\bin | |
| May 10, 2016 at 16:32 | answer | added | lawlist | timeline score: 2 | |
| May 10, 2016 at 16:13 | comment | added | lawlist |
Try this: (setq doc-view-ghostscript-program "/path/to/gs") In my experience, the exec-path is for things like helping Emacs to create the *Completions* buffer -- however, that is unrelated to helping Emacs find an executable to start a process as that relies upon the environmental variable for the $PATH. You can see what your $PATH by typing: M-x eval-expression RET (getenv "PATH") RET
|
|
| May 10, 2016 at 8:58 | comment | added | wvxvw |
It probably should be exec-path, not load-path. Also, how exactly did you set environment variables (through Windows dialog, or by calling setenv in Emacs?). What shell are you running in Emacs (is it Cygwin's bash or cmd.exe?). If it is cmd.exe, what happens if you type in shell where gsview32?
|
|
| May 10, 2016 at 7:18 | history | asked | myotis | CC BY-SA 3.0 |