Re: [NTG-context] some patches
frantisek holop wrote: hmm, on Mon, May 15, 2006 at 09:23:21AM +0200, Hans Hagen said that (btw, is there a clever way to avoid this sudo stuff and become real root?) i think i missed why you need to become root. is this for regular runs of context in the future? no, i need it just for experimenting / debugging Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
Dalyoung Jeong wrote: Dear Hans, Thank you for your answer. Since it worked perfectly before, I created XeTeX-ConTeXt format using texexec --make --xtx en for a test and run texexec --xtx file.tex. It run OK and I got a pdf output. I think that it is not only the font problem unless texmfstart uses fonts differently. So my wonder is what cause the difference between texmfstart texexec --xetex file.tex and texexec --xtx file.tex.(no output with errors and good output). I am sorry to list this which is the problem for me only. Since my TeX-knowledge is very short, I couldn't do anyting but testing. I'll upgrade to the latest version soon and see how it runs, although I am afraid of upgrading the current ConTeXt(05-11) to the latest one. for xetex you really need to update because the backend driver has changed to xpdfmx Hans ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
for xetex you really need to update because the backend driver haschanged to xpdfmxHansDear Hans,Thank you for the reply.I'll upgrade to the latest version soon. By the way, I noticed one thing in the process of XeTeX-ConTeXt.In the previous version before may, "texexec --xtx file.tex" run and made file.xdv, and then finally produced file.pdf.But in the current version "texmfstart texexec --xetex file.tex" run and file.tuo - file.dvi - file.pdf are produced in the log file but file.pdf is not produced in the folder. "texexec --xtx file.tex" also produced pdf via *.tuo - *.dvi - *.pdf but figures in pdf format are appeared as blank space.Doesn't ConTeXt-XeTeX use *.xdv anymore?I'd like to upgrade from the beginning, TeX+ConTeXt update + XeTeX and test the same file.It makes me a little bit nervous.Thank you again.Dalyoung___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches (clever ConTeXt installation)
Le 16 mai 06 à 01:14, Hans Hagen a écrit : Maurice Diamantini wrote:nment. Usually, one can build dynamicaly (default) variable environment at the start of a programm (i.e. in the same process and sub-process), then let the original environment untouch while ending the programm. this is what texmfstart --tree= texexec does; it sets env vars specified in either setuptex.tmf in the path mentioned as tree, or some specific tmf file; those tmf files are platform independent. this is how i run multiple (different trees) on one machine (say a web server); Thank you very much. So I can do a little texexec script, add its path in front of the global path (so that it will be found before any standard old ConTeXt distrib) and use the new texexec shell script as the main context executable as usualy. The main avantage over my previous proposal is that it doesn't even require adding a new path in the PATH environment variable (which already is quite accectable!). I don't know much about context, but if you use some texmfstart laucher, it could have the responsability of that job). In fact, I'd like to only have to add some PATH for using a personnal full ConTeXt distribution near another standard LaTeX (containing obolate Context) this is what in regular distributions texmf-local is for Yes, but the texmf-local is part of a particular directory from a particular network or host. And I like to separate my own (full, independant, robust, ...) ConTeXt environmement from the several LaTeX distrib I use (e.g. my unix/osX account is mirror via rsync between hom, work, and another network. LaTeX will probably become again my main xTeX environment, but I'd like to be able to switch ponctualy to a recent ConTeXt distro, without hacking and breaking my main TeX environment. in that case, just put the latest context in your main tree (unzip cont-tmf in texmf-local or so); that should work as always No, because of recent font (lm) probleme, I decided to keep a full context distrib (linuxtex.zip + macosxtex.zip + justtex.zip) in my personnal home directory. I positionned this environment with some setuptex variante before using context program (with all previous problems when comming back to LaTeX) Because the Makefile should work on all plateform (and in a year or two also if possible!) I use only the standard texexec (instead of texmfstart and path argument). But if you say texmfstart become the standard way: I'd switch to! well, you can still use texexec.rb instead of texexec.pl and avoid texmfstart; it's just that then you need to keep an eye on when texexec changes Do you mean that texexec.rb is clever enought to guess its ows directory tree ? Great, that what I asked for ;-) (and if texexec.rb becomme the standard texexec tool the problem is solved (no more need to do a small texexec shell script) but... ... for context programme only, but what about other tools (metapost, mp2pdf...) Just a remark in that case: texmfstart seems a bad name, bacause not related to ConTeXt Why not simply context or ctx as the main ConTeXt tool?) because i use it to run anything organized in a tree (e.g. xsltproc); running context progies i just part of the game Ok, I can always make an alias ctx for texmfstart --tree=... alias ctx=texmfstart --tree=/home/myHome/myLocl/fullcontext perhaps it solves all problem at a time! I'll try that in the next two week. Thank you very much, Maurice ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
Dalyoung wrote: for xetex you really need to update because the backend driver has changed to xpdfmx Hans Dear Hans, Thank you for the reply. I'll upgrade to the latest version soon. By the way, I noticed one thing in the process of XeTeX-ConTeXt. In the previous version before may, texexec --xtx file.tex run and made file.xdv, and then finally produced file.pdf. But in the current version texmfstart texexec --xetex file.tex run and file.tuo - file.dvi - file.pdf are produced in the log file but file.pdf is not produced in the folder. texexec --xtx file.tex also produced pdf via *.tuo - *.dvi - *.pdf but figures in pdf format are appeared as blank space. Doesn't ConTeXt-XeTeX use *.xdv anymore? not by default; esp since xdvipdfmx will become the real thing for xetex Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
Hi, On 5/15/06, Hans Hagen [EMAIL PROTECTED] wrote: (btw, is there a clever way to avoid this sudo stuff and become real root?) I personnaly do: sudo -s when I need to become root for several commands. And then I: exit Gilles. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
(btw, is there a clever way to avoid this sudo stuff and become real root?) Ubuntu Linux also uses sudo instead of a root login. There I get around it with: $ sudo bash (or your favorite shell) Password: ... # cmd1 ... -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
Le 15 mai 06 à 09:23, Hans Hagen a écrit : Hi, I played a bit with texmfstart on the (so so slow Q3) mac and i think that i managed to get texmfstart working with less problems. I now also ship a texmfstart with all the used (context/ruby/base) libraries merged in (new undocumented feature) so that there is no longer a need to set the ruby lib path and/or move base files. The new version is uploaded. A next step is to get the stubs done in the right way (just texmfstart scriptname args) Not quite related to this subject, but as you are going to make the ConTeXt installation more and more robust. It would be nice if the ConTeXt independant distrib could be use **without positionning any TEXMF like variables**. This would allow to use updated ConTeXt distrib without breaking a standard (more or less old) other LaTeX existing distibution. -- Maurice Diamantini ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
Maurice Diamantini wrote: Le 15 mai 06 � 09:23, Hans Hagen a �crit : Hi, I played a bit with texmfstart on the (so so slow Q3) mac and i think that i managed to get texmfstart working with less problems. I now also ship a texmfstart with all the used (context/ruby/base) libraries merged in (new undocumented feature) so that there is no longer a need to set the ruby lib path and/or move base files. The new version is uploaded. A next step is to get the stubs done in the right way (just texmfstart scriptname args) Not quite related to this subject, but as you are going to make the ConTeXt installation more and more robust. It would be nice if the ConTeXt independant distrib could be use **without positionning any TEXMF like variables**. This would allow to use updated ConTeXt distrib without breaking a standard (more or less old) other LaTeX existing distibution. hm, in principle you can put the minimal over an existing big one and cross your fingers for it to work. the problem with the texmf vars's is that some of them are hard coded (sigh) and the reason why i provide the 'setuptex' things is that when i install tex on some system, i want to be sure that there are no interferences (in the past tex was often installed on linxu systems by default and the only robust way to get rid of an exiting setup was to overload all relevant texmf related vars; btw, a inimal installation will not break anything exiting, since you can put it somewhere else; you can even get away from the setuptex scripts by running texmfstart --tree=/say/its/located/here texexec ... which is handy in web based environments; in that case, texmfstart will read the setuptex.tmf file Hans Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl - ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
On 15 May 2006, at 09:23, Hans Hagen wrote: (btw, is there a clever way to avoid this sudo stuff and become real root?) This depends on what you want to do and on which system. On most unixes, you can say. You can in perl (and probably also ruby which I do not know) set all kinds of unixy things like real uid ($) and effective uid ($) as long as you already have the permissions. sudo -H -s to become root and also have root's home directory. G ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
hmm, on Mon, May 15, 2006 at 09:23:21AM +0200, Hans Hagen said that (btw, is there a clever way to avoid this sudo stuff and become real root?) i think i missed why you need to become root. is this for regular runs of context in the future? -f -- will you leave me alone if i give you a quote? -- emmanuel goldstein ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] some patches
Dear Hans, Thank you for your answer. Since it worked perfectly before, I created XeTeX-ConTeXt format using texexec --make --xtx en for a test and run texexec --xtx file.tex. It run OK and I got a pdf output. I think that it is not only the font problem unless texmfstart uses fonts differently. So my wonder is what cause the difference between texmfstart texexec --xetex file.tex and texexec --xtx file.tex.(no output with errors and good output). I am sorry to list this which is the problem for me only. Since my TeX-knowledge is very short, I couldn't do anyting but testing. I'll upgrade to the latest version soon and see how it runs, although I am afraid of upgrading the current ConTeXt(05-11) to the latest one. Thank you again. Best regards, Dalyoung ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
