Peter Dyballa
Peter_Dybal****@Web*****
Wed Dec 20 10:00:04 JST 2006
Am 20.12.2006 um 00:34 schrieb Roussanka Loukanova:
>
> I guess, I have to replace "latex" with the dvips, ps2pdf commands,
> but what exactly should I type there?
No, no: you need to add one or two new commands first. It's
standardised under the "TeX Command List" item. Pressing the INS
button creates a new form. I think the manual can explain it better,
what to do and and what to check and why and if at all ... The item
"TeX Expand List" explains a bit what these things in () or with % mean.
>
>> Again, since you need to add a command to the Commands menu, think of
>> adding a shell script as a PSTricks command. Herb Schulz' ps4pdf
>> engine script goes (a bit edited by me):
>
> Do I have to copy and paste this code in some file? (sorry for the
> stupid question: I've never done such things up to now).
Yes. The file should not be named ps4pdf, because this is already
used by another file (ps4pdf.sh would work). The script file should
go into the bin folder in your home directory. Once it's saved, you'd
need to make it executable (with Finder's inspector for example, or
on the command line in Terminal: "chmod a+x <file name>").
>
>
>> accommodate the texdoc script to use particular applications for
>> particular file formats – and texdoc is in my AUCTeX the Viewer. To
>> save my custom texdoc script from being erased by an i-Package update
>> I've put into my ~/bin directory, which is in the search path for
>> executables.
>
> I will create such too, but what exactly to put in it?
> It seems I've understood the lesson quite ok, but without being
> able to do something pragmatical :(
Programmatically? Copy the texdoc script from the same location as
dvips or latex to your bin directory (on the command line it's these
two commands that also make sure that your bin sub-directory exists:
mkdir ~/bin ; cp `which texdoc` ~/bin). At lines around #80...90 of
your copy of the texdoc script you can change the right hand side for
example to:
: ${TEXDOCVIEW_dvi='open -a TeXShop\ 2.app %s'}
: ${TEXDOCVIEW_pdf='open -a TeXShop\ 2.app %s'}
: ${TEXDOCVIEW_ps='open -a TeXShop\ 2.app %s'}
: ${TEXDOCVIEW_html='open -a OmniWeb.app %s'}
: ${TEXDOCVIEW_txt="emacsclient %s"}
: ${TEXDOCVIEW_="emacsclient %s"} # no extension, default to pager
Actually the .app extension is not necessary, the Mac OS X launch
service finds the real programme in /Applications/<application
name>.app/Contents/MacOS/, so just substitute "TeXShop\ 2.app"
everytime with "Preview"! The last two lines could be substituted by
'open -a TextEdit %s' – which from time to time fails to open text
files ...
>
> I've tried it and it works, but I prefer the Preview program for
> viewing and even for presentations because it gives me good control
> over jumping over pages back and forth (I even prefer Preview
> instead of Acrobat reader).
That's natural and human.
--
Mit friedvollen Grüßen
Pete
There's no sense in being precise when you don't even know what
you're talking about.
-- John von Neumann