Re: [O] Problem exporting to PDF (and viewing)

[Jonathan Leech-Pepin]

I suspect you should be able to get it to recognize "C:/Program\
Files/sumatrapdf/sumatrapdf.exe".

Alternately if the exe is found on your PATH (you may need to add it
by hand), you should be able to manage with:

    (executable-find "sumatrapdf.exe")

which should be able to track back the path to the appropriate file.

On Sat, May 12, 2012 at 12:10 AM, Richard Stanton
<address@hidden> wrote:
> Checking further, this works fine using the default Windows shell in Emacs, 
> but fails if I use bash as my shell. Unfortunately, I like to use bash, which 
> I achieve with the following lines in my init.el:
>
>      (setq shell-file-name "bash")
>      (setenv "SHELL" shell-file-name)
>      (setq explicit-shell-file-name shell-file-name)
>
>> -----Original Message-----
>> From: Richard Stanton
>> Sent: Friday, May 11, 2012 4:52 PM
>> To: address@hidden
>> Subject: Problem exporting to PDF (and viewing)
>>
>> Using Org-mode version 7.8.09 (release_7.8.09-553-g5750f0) (and earlier
>> versions) I've encountered a problem on my Windows machine when I try to
>> export an Org file to LaTeX, then to Pdf, then viewing (using C-c C-e d).
>>
>> In my init.el I have the lines
>>
>>   (eval-after-load "org"
>>     '(progn
>>        (if (assoc "\\.pdf\\'" org-file-apps)
>>            (setcdr (assoc "\\.pdf\\'" org-file-apps)
>> "c:/progra~1/sumatrapdf/sumatrapdf.exe  %s")
>>          (add-to-list 'org-file-apps '("\\.pdf\\'" .
>> "c:/progra~1/sumatrapdf/sumatrapdf.exe %s") t))))
>> )
>>
>> This results in:
>>
>> org-file-apps is a variable defined in `org.el'.
>> Its value is ((auto-mode . emacs)
>>  ("\\.mm\\'" . default)
>>  ("\\.x?html?\\'" . default)
>>  ("\\.pdf\\'" . "c:/progra~1/sumatrapdf/sumatrapdf.exe %s"))
>>
>> When I try to export an org file by typing C-c C-e d, sumatrapdf opens up OK,
>> but complains with an error like this:
>>
>> Error loading c:\dropbox\org\c\:\dropbox\org\personal.pdf
>>
>> Any idea why I get the repeated path? A similar constructions works fine on
>> my Mac, so I'm not quite sure what's going wrong here.
>
>