On Tue, 6 May 2008, franconi wrote:
...
>> 1. I've tried simpdftexnodel.sh from
>> <http://phaseportrait.blogspot.com/2007/07/skim-automatic-refreshes-an...>
>> But it goes into a loop, both from Emacs (after I have created an AUCTeX
>> command for it) and in Terminal. The later tells that the problem is not
>> from Emacs' settings.
>
> I am regularly using a variant of simpdftexnodel and I have no
> problems at all. Which kind of "loop" are you talking about?

I tried both

simpdftexnodel.sh latex --maxpfb file.tex
and
simpdftexnodel.sh file.tex

from Emacs (after I have created an AUCTeX command) and in Terminal.
By leaving the loop for awhile on its own, in Terminal, I see the
errors copied below, after a long repetitions of the first two lines:

It seems that dvips can't be used by simpdftexnodel.sh. But otherwise, I 
can run "simpdftex latex --maxpfb file.tex", "dvips file.dvi".
...
### /Users/rosi/bin/simpdftexnodel.sh latex
### This is /Users/rosi/bin/simpdftexnodel.sh, Version 20070712
/Users/rosi/bin/simpdftexnodel.sh: fork: Resource temporarily unavailable
/Users/rosi/bin/simpdftexnodel.sh: fork: Resource temporarily unavailable
/Users/rosi/bin/simpdftexnodel.sh: fork: Resource temporarily unavailable
### Skipping   [dvi->pdf only]
### /Users/rosi/bin/dvips -R -Poutline  -o
/tmp/altpdf.15953-1209989766/.ps latex
/Users/rosi/bin/simpdftexnodel.sh: line 473: /Users/rosi/bin/dvips: No
such file or directory
### FAILED to generate /tmp/altpdf.15953-1209989766/.ps ()
### WARNING: TeX returned non zero exit status
### /Users/rosi/bin/dvips -R -Poutline  -o
/tmp/altpdfsimpdftexnodel.sh.15935-1209989766/latex.ps latex.dvi
/Users/rosi/bin/simpdftexnodel.sh: line 473: /Users/rosi/bin/dvips: No
such file or directory
### FAILED to generate
/tmp/altpdfsimpdftexnodel.sh.15935-1209989766/latex.ps ()
### WARNING: TeX returned non zero exit status
...:


Roussanka

--~--~---------~--~----~------------~-------~--~----~
Carbon Emacs User Group
http://groups.google.com/group/carbon-emacs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to