status message of mtxrun --ifchanged
Hi, When I run mtxrun --ifchanged, it echoes the status messages on stdout. This makes it impossible to use mtxrun --ifchanged as part of a standard unix pipe. What is the right way to resolve this? * Output these messages to stderr rather than stdout? * Provide a --silent option mtxrun that suppresses all output? I can parse the generated output and remove the lines starting with MTXrun, but that is no fun. Aditya
On 11-6-2010 4:19, Aditya Mahajan wrote:
Hi,
When I run mtxrun --ifchanged, it echoes the status messages on stdout. This makes it impossible to use mtxrun --ifchanged as part of a standard unix pipe. What is the right way to resolve this?
* Output these messages to stderr rather than stdout? * Provide a --silent option mtxrun that suppresses all output?
I can parse the generated output and remove the lines starting with MTXrun, but that is no fun.
after discussing it (as well as more generic suppresion message in the engine) taco and i decided to go for --verbose instead new beta Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Sat, 12 Jun 2010, Hans Hagen wrote:
On 11-6-2010 4:19, Aditya Mahajan wrote:
Hi,
When I run mtxrun --ifchanged, it echoes the status messages on stdout. This makes it impossible to use mtxrun --ifchanged as part of a standard unix pipe. What is the right way to resolve this?
* Output these messages to stderr rather than stdout? * Provide a --silent option mtxrun that suppresses all output?
I can parse the generated output and remove the lines starting with MTXrun, but that is no fun.
after discussing it (as well as more generic suppresion message in the engine) taco and i decided to go for --verbose instead
new beta
Updating using first-setup.sh gives (also tried a fresh install, the same error) sent 32402 bytes received 7755726 bytes 65172.62 bytes/sec total size is 30315844 speedup is 3.89 MTXrun | run: rsync -rpztlv contextgarden.net::'minimals/current/misc/setuptex/' '/tmp/context/tex/.' receiving incremental file list ./ setuptex setuptex.bat setuptex.csh setuptex.tmf sent 109 bytes received 6545 bytes 1209.82 bytes/sec total size is 16420 speedup is 2.47 MTXrun | mtx update: updating mtxrun for linux-64: rsync -tgo --chmod=a+x /tmp/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /tmp/context/tex/texmf-linux-64/bin/mtxrun MTXrun | run: rsync -tgo --chmod=a+x /tmp/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /tmp/context/tex/texmf-linux-64/bin/mtxrun /tmp/context/bin/mtxrun:8497: bad argument #3 to 'format' (string expected, got no value) I am on linux-64, if that matters. Aditya
On Jun 13, 2010, at 1:49 AM, Aditya Mahajan wrote:
Updating using first-setup.sh gives (also tried a fresh install, the same error)
sent 32402 bytes received 7755726 bytes 65172.62 bytes/sec total size is 30315844 speedup is 3.89 MTXrun | run: rsync -rpztlv contextgarden.net::'minimals/current/misc/setuptex/' '/tmp/context/tex/.' receiving incremental file list ./ setuptex setuptex.bat setuptex.csh setuptex.tmf
sent 109 bytes received 6545 bytes 1209.82 bytes/sec total size is 16420 speedup is 2.47 MTXrun | mtx update: updating mtxrun for linux-64: rsync -tgo --chmod=a+x /tmp/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /tmp/context/tex/texmf-linux-64/bin/mtxrun MTXrun | run: rsync -tgo --chmod=a+x /tmp/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /tmp/context/tex/texmf-linux-64/bin/mtxrun /tmp/context/bin/mtxrun:8497: bad argument #3 to 'format' (string expected, got no value)
Same error here on OS X. And another question: I couldn't get my TEXMFHOME recognized under linux-32. One problem was that it is set to ~/texmf-home. I would suggest setting this value back to the canonical ~/texmf. (I had more problems, but I'll have to reboot into linux in order to verify). All best Thomas
On Jun 13, 2010, at 9:33 AM, Thomas A. Schmitz wrote:
Same error here on OS X. And another question: I couldn't get my TEXMFHOME recognized under linux-32. One problem was that it is set to ~/texmf-home. I would suggest setting this value back to the canonical ~/texmf. (I had more problems, but I'll have to reboot into linux in order to verify).
OK, this problem is gone with the latest beta. The problem with the wrong value of TEXMFHOME persists. In a pristine texmfcnf.lua, this is set (l. 25) TEXMFHOME = "~/texmf-home", -- "tree:///~/texmf for mkii, however, it is set in texmf.cnf (l. 31) TEXMFHOME = $HOME/texmf why these two different values? I consider texmf-home as wrong. Moreover, when I set this to a sane value TEXMFHOME = "/Users/tas/texmf", -- "tree:///~/texmf and then re-run mtxrun --generate, I get this error: MTXrun | MTXrun | fileio: scanning path 'tree:////Users/tas/texmf' /Users/tas/context/tex/texmf-osx-64/bin/mtxrun:9094: cannot open tree:////Users/tas/texmf/: No such file or directory I have no idea what the notation 'tree:////' is supposed to do. /Users/tas/texmf does indeed exist and works with the beta before the scripts were changed. So I'm somewhat stymied. Thomas
On 13-6-2010 7:32, Thomas A. Schmitz wrote:
On Jun 13, 2010, at 9:33 AM, Thomas A. Schmitz wrote:
Same error here on OS X. And another question: I couldn't get my TEXMFHOME recognized under linux-32. One problem was that it is set to ~/texmf-home. I would suggest setting this value back to the canonical ~/texmf. (I had more problems, but I'll have to reboot into linux in order to verify).
OK, this problem is gone with the latest beta. The problem with the wrong value of TEXMFHOME persists. In a pristine texmfcnf.lua, this is set (l. 25)
TEXMFHOME = "~/texmf-home", -- "tree:///~/texmf
for mkii, however, it is set in texmf.cnf (l. 31)
TEXMFHOME = $HOME/texmf
why these two different values? I consider texmf-home as wrong.
because i dislike having a 'texmf' other than the main one anywhere (if only because it makes tracing a pain) .. i'll set it to texmf but will probably add some warnings in a future version
Moreover, when I set this to a sane value
TEXMFHOME = "/Users/tas/texmf", -- "tree:///~/texmf
and then re-run mtxrun --generate, I get this error:
MTXrun | MTXrun | fileio: scanning path 'tree:////Users/tas/texmf' /Users/tas/context/tex/texmf-osx-64/bin/mtxrun:9094: cannot open tree:////Users/tas/texmf/: No such file or directory
strange as that should be intercepted. I'll see what my mac does with it when i hav eit up and running.
I have no idea what the notation 'tree:////' is supposed to do. /Users/tas/texmf does indeed exist and works with the beta before the scripts were changed. So I'm somewhat stymied.
tree:// is just one of the uri's supported (and permits loading files from some tree) and this scheme is autoinserted when no !! is used; the !! will become cache:// .. much of that is still experimental Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Jun 13, 2010, at 10:58 PM, Hans Hagen wrote:
On 13-6-2010 7:32, Thomas A. Schmitz wrote:
TEXMFHOME = "~/texmf-home", -- "tree:///~/texmf
for mkii, however, it is set in texmf.cnf (l. 31)
TEXMFHOME = $HOME/texmf
why these two different values? I consider texmf-home as wrong.
because i dislike having a 'texmf' other than the main one anywhere (if only because it makes tracing a pain) .. i'll set it to texmf but will probably add some warnings in a future version
Well, I know that, we've been discussing it for a while. But then both mkii and mkiv still should have the same value. And ~/texmf is the canonical thing; disregarding it will confuse any casual user.
strange as that should be intercepted. I'll see what my mac does with it when i hav eit up and running.
I get the same behavior on linux.
tree:// is just one of the uri's supported (and permits loading files from some tree) and this scheme is autoinserted when no !! is used; the !! will become cache:// .. much of that is still experimental
OK, thanks for the info. I used to have my own configuration, but environment variables aren't used any more. How does mkiv store the config information now? How could I overwrite the values that mtxrun --variables shows? All best Thomas
On Sun, Jun 13, 2010 at 23:06, Thomas A. Schmitz wrote:
OK, thanks for the info. I used to have my own configuration, but environment variables aren't used any more. How does mkiv store the config information now? How could I overwrite the values that mtxrun --variables shows?
I didn't test, but creating your own version of texmfcnf.lua inside texmf-local/web2c might help, though I didn't test it (it might be a chicken-and-egg problem to locate that lua file, but texmf-local should work; if it doesn't, one should better fix it). I'm working on someone else's computer and don't find it too comfortable to test anything from here (I'm not even able to type on qwerz any more). I see there were many other error reports in the last few days as well ... Mojca
On 13-6-2010 11:13, Mojca Miklavec wrote:
I'm working on someone else's computer and don't find it too comfortable to test anything from here (I'm not even able to type on qwerz any more). I see there were many other error reports in the last few days as well ...
i'm looking into it ... one problem is that we run a mtxrun underbin while the real mtxrun later sits under texmf-* and this confuses the logic that generates the databases these are all side effects of future multiple cache support and playing nice with texlive related vars and that has to work with all kind of setups in the end it will work Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 13-6-2010 11:06, Thomas A. Schmitz wrote:
OK, thanks for the info. I used to have my own configuration, but environment variables aren't used any more. How does mkiv store the config information now? How could I overwrite the values that mtxrun --variables shows?
environment variables should still win from variables set in the configuration file (if it needs to be fixed) but there is some new discovery code i didn't test it yet, but you can have your own configration file and it will be loaded too (and merged where the first loaed var wins) in principle it works like texmf.cnf but in the future we might have more options in the (now used) lua variant Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 13-6-2010 1:49, Aditya Mahajan wrote:
On Sat, 12 Jun 2010, Hans Hagen wrote:
On 11-6-2010 4:19, Aditya Mahajan wrote:
Hi,
When I run mtxrun --ifchanged, it echoes the status messages on stdout. This makes it impossible to use mtxrun --ifchanged as part of a standard unix pipe. What is the right way to resolve this?
* Output these messages to stderr rather than stdout? * Provide a --silent option mtxrun that suppresses all output?
I can parse the generated output and remove the lines starting with MTXrun, but that is no fun.
after discussing it (as well as more generic suppresion message in the engine) taco and i decided to go for --verbose instead
new beta
Updating using first-setup.sh gives (also tried a fresh install, the same error)
sent 32402 bytes received 7755726 bytes 65172.62 bytes/sec total size is 30315844 speedup is 3.89 MTXrun | run: rsync -rpztlv contextgarden.net::'minimals/current/misc/setuptex/' '/tmp/context/tex/.' receiving incremental file list ../ setuptex setuptex.bat setuptex.csh setuptex.tmf
sent 109 bytes received 6545 bytes 1209.82 bytes/sec total size is 16420 speedup is 2.47 MTXrun | mtx update: updating mtxrun for linux-64: rsync -tgo --chmod=a+x /tmp/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /tmp/context/tex/texmf-linux-64/bin/mtxrun MTXrun | run: rsync -tgo --chmod=a+x /tmp/context/tex/texmf-context/scripts/context/lua/mtxrun.lua /tmp/context/tex/texmf-linux-64/bin/mtxrun /tmp/context/bin/mtxrun:8497: bad argument #3 to 'format' (string expected, got no value)
some tracing issue ... can you print(fmt,...) in simple and see what logs.report is involved? local function simple(fmt,...) if fmt then -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (5)
-
Aditya Mahajan -
Hans Hagen -
luigi scarso -
Mojca Miklavec -
Thomas A. Schmitz