Hello:)
First I do not understand the changes in this script.
Certain users prefer to work with latex but without pstricks, why not make two different scripts.
There is a little change in one line :
now if [ -s "${PDF}" -a ! "$PDF" -ot "$FILE" ]; then
before if [ -s "${PDF}" -a "$PDF" -nt "$FILE" ]; then .....
-ot instead -nt ? why ?
Greetings Alain Matthes
On Apr 2, 2007, at 2:33 PM, Alain Matthes wrote:
There is a little change in one line :
now if [ -s "${PDF}" -a ! "$PDF" -ot "$FILE" ]; then
before if [ -s "${PDF}" -a "$PDF" -nt "$FILE" ]; then .....
-ot instead -nt ? why ?
The first condition is negated by the "!", so it reads as "not older than". The second condition reads as "newer than". So ultimately they are equivalent.
On 3. Apr 2007, at 03:21, Dan Lowe wrote:
On Apr 2, 2007, at 2:33 PM, Alain Matthes wrote:
There is a little change in one line :
now if [ -s "${PDF}" -a ! "$PDF" -ot "$FILE" ]; then
before if [ -s "${PDF}" -a "$PDF" -nt "$FILE" ]; then .....
-ot instead -nt ? why ?
The first condition is negated by the "!", so it reads as "not older than". The second condition reads as "newer than". So ultimately they are equivalent.
Except for the case where the PDF file has exactly the same date as the document file.
Here the new version will still continue (with showing the PDF) where the old one would not (thus the change).
Le 3 avr. 07 à 05:18, Allan Odgaard a écrit :
On 3. Apr 2007, at 03:21, Dan Lowe wrote:
On Apr 2, 2007, at 2:33 PM, Alain Matthes wrote:
There is a little change in one line :
now if [ -s "${PDF}" -a ! "$PDF" -ot "$FILE" ]; then
before if [ -s "${PDF}" -a "$PDF" -nt "$FILE" ]; then .....
-ot instead -nt ? why ?
The first condition is negated by the "!", so it reads as "not older than". The second condition reads as "newer than". So ultimately they are equivalent.
Except for the case where the PDF file has exactly the same date as the document file.
Here the new version will still continue (with showing the PDF) where the old one would not (thus the change).
Thanks and sorry !
i need to work because I try to learn how to make my own script so I try to understand this one. In my bash book , -nt et -ot are the last operators for file test :(
Alain Matthes
On Apr 2, 2007, at 2:33 PM, Alain Matthes wrote:
Hello:)
First I do not understand the changes in this script.
Certain users prefer to work with latex but without pstricks, why not make two different scripts.
Sorry, I don't really follow you here. Can't you just tell TM to use latex instead? The %!TEX-program directive should work just like in TeXShop.
Haris Skiadas Department of Mathematics and Computer Science Hanover College
Le 3 avr. 07 à 04:54, Charilaos Skiadas a écrit :
On Apr 2, 2007, at 2:33 PM, Alain Matthes wrote:
Hello:)
First I do not understand the changes in this script.
Certain users prefer to work with latex but without pstricks, why not make two different scripts.
Sorry, I don't really follow you here. Can't you just tell TM to use latex instead? The %!TEX-program directive should work just like in TeXShop.
Hello haris, it's difficult to explain because my english is poor and i'm a very newbie with the shell script, perhaps I don't understand the script.
first I work with Texshop only if i want to test a tex file with dvi + ps because with the mac there are a lot of possiblities :
i try to be clear :
1) latex (dvi + ps) problem
a) it's not necessary to use pstricks. A lot of linux users prefer latex ( dvi + ps) because ...they can use "special" command with PS. And when a linux user work with the mac, often, he works with tex + ghoscript !
b) dvi2ps is not an obligation, with the mac you can prefer dvitops the apple distiller ( with texhop in the pref, you can choose the distiller apple or ghoscript) The apple distiller is not very good but it exists.
c) perhaps i don't understand the script but you can use a latex class or a package who calls pstricks. I'm not sure that's the script detects that ...
d) I work only with pdflatex but i make packages and classes so i need to test my work with pdflatex with the two ways : pdf directly ( the good way for me) and dvi + ps.
e) it's more elegant to work with only one script but in this case perhaps it's more easy to define a shell variable : TM_LATEX_Option : DVI with PDF by default.
2) modify the script ...
with the old script, i made a special variant of the script call "preview"
often i make piece of tex code and i want to compile this piece without complete the file
example : i want to have a look at the result of :
\begin{enumerate}\setlength{\itemsep}{15pt} \item aaa \item bb \item cc \end{enumerate}
so in the script i've
# DIR=`dirname "$M"` # FILE=`basename "$M"`
DIR="/Users/ego/Boulot/temp" FILE="temptex.tex"
and after that
cd ${TM_DIR_FOR_TEMP} cat >temptex.tex<<EOF \documentclass[$MY_OPT]{$MY_CLASS} \thispagestyle{empty} \begin{document} \input $M \end{document} EOF
i have some difficulties to insert that with the new script. I'm a really newbie
i make this but it's very brutal :
run_tex () { "$TEX" ${TM_LATEX_OPTIONS:=--shell-escape -interaction=nonstopmode - file-line-error-style} "$1" }
# Compile. run_tex "$FILE"
open -a "$V" temptex.pdf html_footer
Greetings Alain Matthes [ www.altermundus.fr ]
PS : I work on the different lists of macro for the completion and my work will be finish in some days . If you a special class for the surveys with QCM, i can make it...
On 4/3/07, Alain Matthes alain.matthes@mac.com wrote:
e) it's more elegant to work with only one script but in this case perhaps it's more easy to define a shell variable : TM_LATEX_Option : DVI with PDF by default.
You can convince the preview script to use ordinary (DVI) latex by setting:
TM_LATEX_COMPILER = latex TEX_PSTRICKS = 1
(Ideally, I think, the first of these would suffice.)
Robin
On Apr 3, 2007, at 2:31 AM, Alain Matthes wrote:
Sorry, I don't really follow you here. Can't you just tell TM to use latex instead? The %!TEX-program directive should work just like in TeXShop.
Hello haris, it's difficult to explain because my english is poor and i'm a very newbie with the shell script, perhaps I don't understand the script.
It's a very complicated script ;) I am working on a cleaner ruby version of it, but it's not quite ready yet.
first I work with Texshop only if i want to test a tex file with dvi + ps because with the mac there are a lot of possiblities : i try to be clear :
- latex (dvi + ps) problem
a) it's not necessary to use pstricks. A lot of linux users prefer latex ( dvi + ps) because ...they can use "special" command with PS. And when a linux user work with the mac, often, he works with tex + ghoscript ! b) dvi2ps is not an obligation, with the mac you can prefer dvitops the apple distiller ( with texhop in the pref, you can choose the distiller apple or ghoscript) The apple distiller is not very good but it exists. c) perhaps i don't understand the script but you can use a latex class or a package who calls pstricks. I'm not sure that's the script detects that ... d) I work only with pdflatex but i make packages and classes so i need to test my work with pdflatex with the two ways : pdf directly ( the good way for me) and dvi + ps. e) it's more elegant to work with only one script but in this case perhaps it's more easy to define a shell variable : TM_LATEX_Option : DVI with PDF by default.
What I am saying is that if you have towards the top of your file the line: %!TEX TS-program = latex then TextMate will use latex+dvi+ps+ps2pdf instead of pdflatex. Is this not what you were asking?
As for the dvi2ps vs dvitops issue, is there anyone not using dvi2ps? If so, what are the reasons?
- modify the script ...
with the old script, i made a special variant of the script call "preview" often i make piece of tex code and i want to compile this piece without complete the file example : i want to have a look at the result of :
\begin{enumerate}\setlength{\itemsep}{15pt} \item aaa \item bb \item cc \end{enumerate}
so in the script i've
# DIR=`dirname "$M"` # FILE=`basename "$M"`
DIR="/Users/ego/Boulot/temp" FILE="temptex.tex"
and after that
cd ${TM_DIR_FOR_TEMP} cat >temptex.tex<<EOF \documentclass[$MY_OPT]{$MY_CLASS} \thispagestyle{empty} \begin{document} \input $M \end{document} EOF
i have some difficulties to insert that with the new script. I'm a really newbie i make this but it's very brutal :
run_tex () { "$TEX" ${TM_LATEX_OPTIONS:=--shell-escape -interaction=nonstopmode - file-line-error-style} "$1" }
# Compile. run_tex "$FILE"
open -a "$V" temptex.pdf html_footer
So is this not working?
If you want to create temporary files, I would suggest doing so in the /tmp directory, instead of the current directory.
Such a command would be very interesting.
Greetings Alain Matthes [ www.altermundus.fr ]
PS : I work on the different lists of macro for the completion and my work will be finish in some days . If you a special class for the surveys with QCM, i can make it...
Haris Skiadas Department of Mathematics and Computer Science Hanover College
Le 4 avr. 07 à 07:04, Charilaos Skiadas a écrit :
What I am saying is that if you have towards the top of your file the line: %!TEX TS-program = latex then TextMate will use latex+dvi+ps+ps2pdf instead of pdflatex. Is this not what you were asking?
ok like TeXshop but .... but now the problem is if the user ptu something on the first line for personnal use, ecause I suppose that %!TEX TS-program = latex must be on the first line. But this is a solution
As for the dvi2ps vs dvitops issue, is there anyone not using dvi2ps? If so, what are the reasons?
Sorry i make a mistake with the names : the steps are : latex --> dvips ---> ps2pdf or pstopdf
The distillers are pstopdf and ps2pdf not dvitopdf ????
For example, Preview.app invokes it(pstopdf ) indifferently when opening PS and EPS files.
In fact, you are three Distillers : epstopdf (teTeX's Distiller but for eps files) , ps2pdf (GhostScript's Distiller) and pstopdf (Apple a product from Adobe but not the real distiller)
And it's more complicated because ps2pdf is a wrapper *************************************************************** t#!/bin/sh # $Id: ps2pdf13 6300 2005-12-28 19:56:24Z giles $ # Convert PostScript to PDF 1.3 (Acrobat 4-and-later compatible). exec ps2pdfwr -dCompatibilityLevel=1.3 "$@" ****************************************************************** And if you transparency or opacity you need to change that 1.4 is needing
Some users prefer apple distiller because Apple uses this tools (Preview) and if you work with a mac you can think that the tools are good ( it's not really the truth but ....). The good distiller is Adobe distiller but it's not free and the others have defaults. But when something goes wrong with one distiller you choose the other like in TeXshop..
i have some difficulties to insert that with the new script. I'm a really newbie i make this but it's very brutal :
run_tex () { "$TEX" ${TM_LATEX_OPTIONS:=--shell-escape -interaction=nonstopmode -file-line-error-style} "$1" }
# Compile. run_tex "$FILE"
open -a "$V" temptex.pdf html_footer
So is this not working?
yes this working and if i work with my bash book perhaps i can make a better one.
If you want to create temporary files, I would suggest doing so in the /tmp directory, instead of the current directory.
yes i know that's the good way but i don't know how to use it ? but i can study examples
Thanks
Greetings Alain
On Apr 4, 2007, at 2:23 AM, Alain Matthes wrote:
Le 4 avr. 07 à 07:04, Charilaos Skiadas a écrit :
ok like TeXshop but .... but now the problem is if the user ptu something on the first line for personnal use, ecause I suppose that %!TEX TS-program = latex must be on the first line.
No, just like in TeXShop it should work if this line appears anywhere in the first 20 lines.
In fact, you are three Distillers : epstopdf (teTeX's Distiller but for eps files) , ps2pdf (GhostScript's Distiller) and pstopdf (Apple a product from Adobe but not the real distiller)
Some users prefer apple distiller because Apple uses this tools (Preview) and if you work with a mac you can think that the tools are good ( it's not really the truth but ....). The good distiller is Adobe distiller but it's not free and the others have defaults. But when something goes wrong with one distiller you choose the other like in TeXshop..
Ok, the question remains though. The script is already complicated enough and I wouldn't want to add a whole new option about distillers until I know there is enough need for that. You can of course just change the corresponding word in the file to the distiller you use,. Or do you often switch between the various distillers? I'll plan to add support for this, along with the option to preview the ps file instead of converting it to pdf, in the Ruby version of the script, but this won't come out for a couple of months probably. So is the ability to switch between distillers really critical? If so, I can see about changing the shell script, but I try to avoid doing that as much as possible.
Thanks
Greetings Alain
Haris Skiadas Department of Mathematics and Computer Science Hanover College
Le 4 avr. 07 à 14:04, Charilaos Skiadas a écrit :
Ok, the question remains though. The script is already complicated enough
yes but with two scripts, the problems would be divided; more users of mac in general works with pdflatex, and the script for pdflatex is simplest. I prefer two scripts like "dvi" and "pdf" and there is no ambiguity and no test and it's more simple for you !
and I wouldn't want to add a whole new option about distillers until I know there is enough need for that. You can of course just change the corresponding word in the file to the distiller you use,. Or do you often switch between the various distillers? I'll plan to add support for this, along with the option to preview the ps file instead of converting it to pdf, in the Ruby version of the script, but this won't come out for a couple of months probably. So is the ability to switch between distillers really critical? If so, I can see about changing the shell script, but I try to avoid doing that as much as possible.
No it's not for me!
I hate dvi + ps !! pdflatex it's very fine for me with Tikz/pgf ( no pstricks)
But if the new script is a Ruby version, i need to learn Ruby... :)
Alain Matthes
On Apr 4, 2007, at 8:36 AM, Alain Matthes wrote:
Le 4 avr. 07 à 14:04, Charilaos Skiadas a écrit :
Ok, the question remains though. The script is already complicated enough
yes but with two scripts, the problems would be divided; more users of mac in general works with pdflatex, and the script for pdflatex is simplest. I prefer two scripts like "dvi" and "pdf" and there is no ambiguity and no test and it's more simple for you !
Hm, that is a possibility. But are there many users who would like to be previewing their files in dvi? And what are the dvi previewers available on Intel machines?
and I wouldn't want to add a whole new option about distillers until I know there is enough need for that. You can of course just change the corresponding word in the file to the distiller you use,. Or do you often switch between the various distillers? I'll plan to add support for this, along with the option to preview the ps file instead of converting it to pdf, in the Ruby version of the script, but this won't come out for a couple of months probably. So is the ability to switch between distillers really critical? If so, I can see about changing the shell script, but I try to avoid doing that as much as possible.
No it's not for me!
I hate dvi + ps !! pdflatex it's very fine for me with Tikz/pgf ( no pstricks)
Ok now I am confused. What are the various compilation paths that you would like to see?
1) pdflatex 2) latex + dvips + ps2pdf 3) .... ?
Or is this not what you are asking?
But if the new script is a Ruby version, i need to learn Ruby... :)
I find that easier than learning Bash ;)
Alain Matthes
Haris Skiadas Department of Mathematics and Computer Science Hanover College
Le 4 avr. 07 à 14:50, Charilaos Skiadas a écrit :
On Apr 4, 2007, at 8:36 AM, Alain Matthes wrote:
Le 4 avr. 07 à 14:04, Charilaos Skiadas a écrit :
Ok, the question remains though. The script is already complicated enough
yes but with two scripts, the problems would be divided; more users of mac in general works with pdflatex, and the script for pdflatex is simplest. I prefer two scripts like "dvi" and "pdf" and there is no ambiguity and no test and it's more simple for you !
Hm, that is a possibility. But are there many users who would like to be previewing their files in dvi? And what are the dvi previewers available on Intel machines?
no dvi it's for dvi --> ps ---> pdf : latex + dvips + ps2pdf
you can make a test and red some news on comp.text.tex or de.comp.text.tex or fr.comp.text.tex without pstricks a lot of people (the majority) work with dvi + ps + pdf and latin1. For me it's a wrong way because pdf and utf8 are the best tools...
No it's not for me!
I hate dvi + ps !! pdflatex it's very fine for me with Tikz/pgf ( no pstricks)
Ok now I am confused. What are the various compilation paths that you would like to see?
- pdflatex
- latex + dvips + ps2pdf
- .... ?
1) for me pdflatex but a simple version that each user can adapt according to his needs
2) now if you want that's a lot of latex's users work with textmate I think that it is important that they can easily compile with latex + dvips + ps2pdf
3) There is a last category of users, those which use gnuplot, asymptote and pst-pdf. a) gnuplot : you need the --shell-escape option if the script is simple is not a problem : for example in my case :
run_tex () { "$TEX" ${TM_LATEX_OPTIONS:=--shell-escape -interaction=nonstopmode -file-line-error-style} "$1" }
b) with asymptote you need to chain scripts : example with asy and pdflatex
run_tex () { location=$(dirname "$1") basefname="${location}/`basename "$1" .tex`"
cd $location pdflatex --shell-escape "$1" echo '<h2>Compiling with Asymptote…</h2>' asy "${basefname}.asy" pdflatex --shell-escape "$1" }
c) with pst-pdf : it's the good way to use pstricks with pdflatex, and you need to use ps4pdf ( google ps4pdf herbert voss)
TEX=${TM_LATEX_COMPILER:=ps4pdf} is easy and the work is fine
It is the reasons for which scripts must be simple, but actually for me TextMate is the best tool to work with Latex.
Perhaps : a good help with comment on the script is a solution
Greetings Alain Matthes
PS : Beginning programmation with Ruby by Chris Pine is a good book for a newbie !
Hey
Just to add another vote for 2 scripts for textmate.
I would love to see dvi--> ps --> pdf as allot of journals (that i publish papers in) still only accept eps figures and as such i must keep using eps and to the best of my knowledge i cant use pdflatex with eps figures. FYI this problem stops allot of my colleagues switching to textmate from texshop as we need this option if we want to submit our papers.
Currently to get around this i just set OPTIONS_program to latex in the shell variables but this is not the best as it stops pdfsync and other nice pdflatex features working when i do not have figures. (also is it possible to get a sync feature working with latex as texshop allows this, if so i had trouble finding the answer with google)
Thanks Jay
ps sorry if this problem has been talked about heaps, i have just switch to textmate so i'm new to the list.
On Apr 4, 2007, at 9:57 AM, Alain Matthes wrote:
Le 4 avr. 07 à 14:50, Charilaos Skiadas a écrit :
On Apr 4, 2007, at 8:36 AM, Alain Matthes wrote:
Le 4 avr. 07 à 14:04, Charilaos Skiadas a écrit :
Ok, the question remains though. The script is already complicated enough
yes but with two scripts, the problems would be divided; more users of mac in general works with pdflatex, and the script for pdflatex is simplest. I prefer two scripts like "dvi" and "pdf" and there is no ambiguity and no test and it's more simple for you !
Hm, that is a possibility. But are there many users who would like to be previewing their files in dvi? And what are the dvi previewers available on Intel machines?
no dvi it's for dvi --> ps ---> pdf : latex + dvips + ps2pdf
you can make a test and red some news on comp.text.tex or de.comp.text.tex or fr.comp.text.tex without pstricks a lot of people (the majority) work with dvi + ps + pdf and latin1. For me it's a wrong way because pdf and utf8 are the best tools...
No it's not for me!
I hate dvi + ps !! pdflatex it's very fine for me with Tikz/pgf ( no pstricks)
Ok now I am confused. What are the various compilation paths that you would like to see?
- pdflatex
- latex + dvips + ps2pdf
- .... ?
- for me pdflatex but a simple version that each user can adapt
according to his needs
- now if you want that's a lot of latex's users work with textmate
I think that it is important that they can easily compile with latex + dvips + ps2pdf
- There is a last category of users, those which use gnuplot,
asymptote and pst-pdf. a) gnuplot : you need the --shell-escape option if the script is simple is not a problem : for example in my case :
run_tex () { "$TEX" ${TM_LATEX_OPTIONS:=--shell-escape -interaction=nonstopmode -file-line-error-style} "$1" }
b) with asymptote you need to chain scripts : example with asy and pdflatex
run_tex () { location=$(dirname "$1") basefname="${location}/`basename "$1" .tex`"
cd $location pdflatex --shell-escape "$1" echo '<h2>Compiling with Asymptote…</h2>' asy "${basefname}.asy" pdflatex --shell-escape "$1" }
c) with pst-pdf : it's the good way to use pstricks with pdflatex, and you need to use ps4pdf ( google ps4pdf herbert voss)
TEX=${TM_LATEX_COMPILER:=ps4pdf} is easy and the work is fine
It is the reasons for which scripts must be simple, but actually for me TextMate is the best tool to work with Latex.
Perhaps : a good help with comment on the script is a solution
Greetings Alain Matthes
PS : Beginning programmation with Ruby by Chris Pine is a good book for a newbie ! ______________________________________________________________________ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Le 4 avr. 07 à 17:25, Jay Gambetta a écrit :
Hey
Just to add another vote for 2 scripts for textmate.
I would love to see dvi--> ps --> pdf as allot of journals (that i publish papers in) still only accept eps figures and as such i must keep using eps and to the best of my knowledge i cant use pdflatex with eps figures. FYI this problem stops allot of my colleagues switching to textmate from texshop as we need this option if we want to submit our papers.
Hello:)
No problem with .eps
\documentclass[]{article}
\usepackage[utf8]{inputenc}
\usepackage[pdftex]{graphicx} \usepackage{epstopdf}
\begin{document}
\begin{figure}[htbp] \centering \includegraphics{fic.eps} \end{figure} \end{document}
And you can compile with pdflatex. I make this with gnuplot and asymptote
Alain Matthes
On Apr 4, 2007, at 11:25 AM, Jay Gambetta wrote:
Hey
Just to add another vote for 2 scripts for textmate.
I would love to see dvi--> ps --> pdf as allot of journals (that i publish papers in) still only accept eps figures and as such i must keep using eps and to the best of my knowledge i cant use pdflatex with eps figures. FYI this problem stops allot of my colleagues switching to textmate from texshop as we need this option if we want to submit our papers.
I have already said twice in this thread that if you include the line: %!TEX TS-program=latex in your first 20 lines, then TextMate will go the dvi->ps->pdf route instead. a) Is this not working? b) Is this not enough? We could have a separate command I suppose, but I really don't see the reason for having 2 different separate commands, which would require of course two different keycombos.
Currently to get around this i just set OPTIONS_program to latex in the shell variables but this is not the best as it stops pdfsync and other nice pdflatex features working when i do not have figures. (also is it possible to get a sync feature working with latex as texshop allows this, if so i had trouble finding the answer with google)
So you would want dvi->ps->pdf when there are figures, and direct pdflatex otherwise? That's hard for TM to decide. I would suggest keeping all figures in both eps and pdf format, then you would be able to use pdfsync most of the time until the final draft, where you would want to disable it anyway since it affects the spacing. This way you don't have to go back and forth between the two compilation methods anyway.
The syncing without pdfsync is not something that can be easily accomplished in TextMate, unfortunately. It requires a very tight coupling between the editor and the viewer. TeXShop really excels there.
Thanks Jay
ps sorry if this problem has been talked about heaps, i have just switch to textmate so i'm new to the list.
On Apr 4, 2007, at 9:57 AM, Alain Matthes wrote:
Le 4 avr. 07 à 14:50, Charilaos Skiadas a écrit :
On Apr 4, 2007, at 8:36 AM, Alain Matthes wrote:
Le 4 avr. 07 à 14:04, Charilaos Skiadas a écrit :
Ok, the question remains though. The script is already complicated enough
yes but with two scripts, the problems would be divided; more users of mac in general works with pdflatex, and the script for pdflatex is simplest. I prefer two scripts like "dvi" and "pdf" and there is no ambiguity and no test and it's more simple for you !
Hm, that is a possibility. But are there many users who would like to be previewing their files in dvi? And what are the dvi previewers available on Intel machines?
no dvi it's for dvi --> ps ---> pdf : latex + dvips + ps2pdf
you can make a test and red some news on comp.text.tex or de.comp.text.tex or fr.comp.text.tex without pstricks a lot of people (the majority) work with dvi + ps + pdf and latin1. For me it's a wrong way because pdf and utf8 are the best tools...
No it's not for me!
I hate dvi + ps !! pdflatex it's very fine for me with Tikz/pgf ( no pstricks)
Ok now I am confused. What are the various compilation paths that you would like to see?
- pdflatex
- latex + dvips + ps2pdf
- .... ?
- for me pdflatex but a simple version that each user can adapt
according to his needs
- now if you want that's a lot of latex's users work with
textmate I think that it is important that they can easily compile with latex + dvips + ps2pdf
- There is a last category of users, those which use gnuplot,
asymptote and pst-pdf. a) gnuplot : you need the --shell-escape option if the script is simple is not a problem : for example in my case :
run_tex () { "$TEX" ${TM_LATEX_OPTIONS:=--shell-escape -interaction=nonstopmode -file-line-error-style} "$1" }
b) with asymptote you need to chain scripts : example with asy and pdflatex
run_tex () { location=$(dirname "$1") basefname="${location}/`basename "$1" .tex`"
cd $location pdflatex --shell-escape "$1" echo '<h2>Compiling with Asymptote…</h2>' asy "${basefname}.asy" pdflatex --shell-escape "$1" }
c) with pst-pdf : it's the good way to use pstricks with pdflatex, and you need to use ps4pdf ( google ps4pdf herbert voss)
TEX=${TM_LATEX_COMPILER:=ps4pdf} is easy and the work is fine
It is the reasons for which scripts must be simple, but actually for me TextMate is the best tool to work with Latex.
Perhaps : a good help with comment on the script is a solution
Greetings Alain Matthes
PS : Beginning programmation with Ruby by Chris Pine is a good book for a newbie ! _____________________________________________________________________ _ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On Apr 4, 2007, at 12:13 PM, Charilaos Skiadas wrote:
I have already said twice in this thread that if you include the line: %!TEX TS-program=latex in your first 20 lines, then TextMate will go the dvi->ps->pdf route instead.
That should probably have been: %!TEX TS-program = latex
There need to be spaces around the = for some reason (TeXShop requires them, so we just followed its convention).
Haris Skiadas Department of Mathematics and Computer Science Hanover College
Le 4 avr. 07 à 18:13, Charilaos Skiadas a écrit :
On Apr 4, 2007, at 11:25 AM, Jay Gambetta wrote:
Hey
Just to add another vote for 2 scripts for textmate.
I would love to see dvi--> ps --> pdf as allot of journals (that i publish papers in) still only accept eps figures and as such i must keep using eps and to the best of my knowledge i cant use pdflatex with eps figures. FYI this problem stops allot of my colleagues switching to textmate from texshop as we need this option if we want to submit our papers.
I have already said twice in this thread that if you include the line: %!TEX TS-program=latex in your first 20 lines, then TextMate will go the dvi->ps->pdf route instead. a) Is this not working? b) Is this not enough? We could have a separate command I suppose, but I really don't see the reason for having 2 different separate commands, which would require of course two different keycombos.
with
\documentclass[]{article}
\usepackage[utf8]{inputenc} \usepackage[pdftex]{graphicx} \usepackage{epstopdf} \usepackage{pdfsync}
\begin{document} Essai
\begin{figure}[htbp] \centering \includegraphics{fic.eps} \end{figure}
Cela fonctionne !
\end{document}
You can compile with pdflatex, import file.eps and have synchronicity
Greetings Alain
Hey
Thanks for your help - i have solved the problem
%!TEX TS-pragram = latex was not working - the reason was the latex document was originally created in windows and it saves it as some line encoding that must put hidden symbols. Now i simply have to save it as the LF encoding and edit away.
Later Jay
%!TEX TS-program=latex
On Apr 4, 2007, at 12:50 PM, Alain Matthes wrote:
Le 4 avr. 07 à 18:13, Charilaos Skiadas a écrit :
On Apr 4, 2007, at 11:25 AM, Jay Gambetta wrote:
Hey
Just to add another vote for 2 scripts for textmate.
I would love to see dvi--> ps --> pdf as allot of journals (that i publish papers in) still only accept eps figures and as such i must keep using eps and to the best of my knowledge i cant use pdflatex with eps figures. FYI this problem stops allot of my colleagues switching to textmate from texshop as we need this option if we want to submit our papers.
I have already said twice in this thread that if you include the line: %!TEX TS-program=latex in your first 20 lines, then TextMate will go the dvi->ps->pdf route instead. a) Is this not working? b) Is this not enough? We could have a separate command I suppose, but I really don't see the reason for having 2 different separate commands, which would require of course two different keycombos.
with
\documentclass[]{article}
\usepackage[utf8]{inputenc} \usepackage[pdftex]{graphicx} \usepackage{epstopdf} \usepackage{pdfsync}
\begin{document} Essai
\begin{figure}[htbp] \centering \includegraphics{fic.eps} \end{figure}
Cela fonctionne !
\end{document}
You can compile with pdflatex, import file.eps and have synchronicity
Greetings Alain ______________________________________________________________________ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-
Alain Matthes -
Allan Odgaard -
Charilaos Skiadas -
Dan Lowe -
Jay Gambetta -
Robin Houston