On Fri, 02 Jul 2010 12:17:15 +0200, luigi scarso wrote:
The same for my linux 64bit box
thanks Li Yanrui
--
---
Martin 'golodhrim' Scholz
Auf dem Sattler 4
34516 Ederbringhausen
Phone: +49 6454 799623
mobile: +49 176 63301749
Fax: +49 6454
e-Mail: scholz@googlemail.com
Oook!
2010/7/2 Li Yanrui (李延瑞) liyanrui...@gmail.com:
2010/7/2 Li Yanrui (李延瑞) liyanrui...@gmail.com:
2010/7/2 Li Yanrui (李延瑞) liyanrui...@gmail.com:
2010/6/30 luigi scarso luigi.sca...@gmail.com:
On Wed, Jun 30, 2010 at 9:36 AM, Alan BRASLAU alan.bras...@cea.fr wrote:
Latest minimals:
2010/7/3 views63 view...@gmail.com:
In this way the log said ConTeXt ver: 2010.05.24 13:05 MKIV fmt:
2010.7.2 int: english/english why? I used the latest.
just my workaround. waitting for Hans to fix it.
--
Best regards,
Li Yanrui (李延瑞)
In this way the log said ConTeXt ver: 2010.05.24 13:05 MKIV
version is defined in context.tex
\edef\contextversion{2010.05.24 13:05}
fmt: 2010.7.2 int: english/english why?
Date of format generation (in your case last time you have build your
format is 2010.7.2)
--
luigi
2010/7/2 luigi scarso luigi.sca...@gmail.com:
On Fri, Jul 2, 2010 at 11:52 AM, Li Yanrui (李延瑞) liyanrui...@gmail.com
wrote:
2010/7/2 Li Yanrui (李延瑞) liyanrui...@gmail.com:
2010/7/2 Li Yanrui (李延瑞) liyanrui...@gmail.com:
2010/6/30 luigi scarso luigi.sca...@gmail.com:
On Wed, Jun 30, 2010 at
2010/7/3 luigi scarso luigi.sca...@gmail.com:
In this way the log said ConTeXt ver: 2010.05.24 13:05 MKIV
version is defined in context.tex
\edef\contextversion{2010.05.24 13:05}
fmt: 2010.7.2 int: english/english why?
Date of format generation (in your case last time you have build your
2010/6/30 luigi scarso luigi.sca...@gmail.com:
On Wed, Jun 30, 2010 at 9:36 AM, Alan BRASLAU alan.bras...@cea.fr wrote:
Latest minimals:
mtxrun:9289: attempt to concatenate local 'v' (a table value)
confirmed on my linux 32 box too
it seems that the following commands can solved this
2010/7/2 Li Yanrui (李延瑞) liyanrui...@gmail.com:
2010/6/30 luigi scarso luigi.sca...@gmail.com:
On Wed, Jun 30, 2010 at 9:36 AM, Alan BRASLAU alan.bras...@cea.fr wrote:
Latest minimals:
mtxrun:9289: attempt to concatenate local 'v' (a table value)
confirmed on my linux 32 box too
it seems
Latest minimals:
mtxrun:9289: attempt to concatenate local 'v' (a table value)
Alan
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : ntg-context@ntg.nl /
On Wed, Jun 30, 2010 at 9:36 AM, Alan BRASLAU alan.bras...@cea.fr wrote:
Latest minimals:
mtxrun:9289: attempt to concatenate local 'v' (a table value)
confirmed on my linux 32 box too
--
luigi
___
If your
Hi,
Under linux x86:
$ context --version
MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
After I replaced the current one with the previous one, it can work again.
--
Best regards,
Li Yanrui
___
If
On Wed, 23 Dec 2009, Yanrui Li wrote:
Hi,
Under linux x86:
$ context --version
MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
Run luatools --generate first.
Aditya
___
If your question is of
2009/12/23 Yanrui Li liyanrui...@gmail.com
Hi,
Under linux x86:
$ context --version
MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
After I replaced the current one with the previous one, it can work again.
Sorry, I discovered this is only my delusion for the result after
2009/12/23 Aditya Mahajan adit...@umich.edu
On Wed, 23 Dec 2009, Yanrui Li wrote:
Hi,
Under linux x86:
$ context --version
MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
Run luatools --generate first.
I do so, but it still don't work. These are my steps:
$ rm -rf
On 23-12-2009 2:08, Yanrui Li wrote:
2009/12/23 Aditya Mahajan adit...@umich.edu mailto:adit...@umich.edu
On Wed, 23 Dec 2009, Yanrui Li wrote:
Hi,
Under linux x86:
$ context --version
MTXrun | unknown script 'context.lua' or 'mtx-context.lua'
Run
Alan BRASLAU wrote:
I did a fresh install of the minimals today and observed a fleeting, obscure
mtxrun bug:
$ context myfile
did not find the script mtx-context.lua
$ mtxrun --script /usr/local/context/tex/texmf-context/\
scripts/context/lua/mtx-context.lua myfile
ran fine, as now does all
I did a fresh install of the minimals today and observed a fleeting, obscure
mtxrun bug:
$ context myfile
did not find the script mtx-context.lua
$ mtxrun --script /usr/local/context/tex/texmf-context/\
scripts/context/lua/mtx-context.lua myfile
ran fine, as now does all subsequent runs of
Henning Hraban Ramm wrote:
##
/texmf/tex/texmf-osx-intel/bin/mtxrun:1953: attempt to call field
'HEXsum' (a nil value)
##
should be
return md5.HEX(data)
Am 2009-05-16 um 13:26 schrieb Hans Hagen:
/texmf/tex/texmf-osx-intel/bin/mtxrun:1953: attempt to call
field 'HEXsum' (a nil value)
should be
return md5.HEX(data)
Yes, that seems to fix the issue. Thank you!
Greetlings from Lake Constance!
Hraban
---
As far as I skimmed the discussions of the last days, this didn't show
up yet:
In my LilyPond module I call the programm like so:
\def\LP{mtxrun --ifchanged=\lily!filename.tmp --exec bin:lilypond -
dbackend=eps -dno-gs-load-fonts -dinclude-eps-fonts -ddelete-
intermediate-files
(Sorry for double-posting, but my first message didn't show up yet,
maybe it's lost. This one is corrected anyway.)
As far as I skimmed the discussions of the last days, this didn't show
up yet:
In my LilyPond module I call the program like so:
\def\LP{mtxrun
Hi Hans,
the following produced a list with all font features for Minion Pro
but it did no longer work.
mtxrun --script fonts --list --info minionproregular
Wolfgang
___
If your question is of interest to
i tend to use --pattern, is that wrong?
$ mtxrun --script fonts --list --info --pattern=*minion*
MTXrun | fontname: minionprobold
MTXrun | fullname: MinionPro-Bold
MTXrun | filename: /media/sdb1/Fonts/Minion Pro/MinionPro-Bold.otf
MTXrun |
MTXrun | fontname: minionproboldcapt
MTXrun | fullname:
Hi,
It seems that mtxrun --noquotes behaves differently on windows and linux.
Can someone on windows (who has vim) check the following. Run
mtxrun --noquotes bin:vim -u NONE -c \set tabstop=8\ test.tex
You will enter in vim. Press :qa! to exit vim. What does the output on the
terminal say?
I think I may not write it clear in my previous email. I run the command as
mtxrun --noquotes bin:vim -u NONE -c \set tabstop=8\ \test.tex\
which got the mtxrun output has spurious before test.tex. if omit the \
around the test.tex, like this,
mtxrun --noquotes bin:vim -u NONE -c \set
On Fri, 10 Apr 2009, Andy Wong wrote:
I think I may not write it clear in my previous email. I run the command as
mtxrun --noquotes bin:vim -u NONE -c \set tabstop=8\ \test.tex\
If you quote the filename, then it should be
mtxrun --noquotes bin:vim -u NONE -c \set tabstop=8\ \test.tex\
Yes, if leave a space between the last two quotes, mtx output seems ok.
MTXrun |
MTXrun | executing: vim -u NONE -c set tabstop=8 test.tex
MTXrun |
But it still cause vim open two file named tabstop=8 and test.tex to
edit. So it seems vim treat tabstop=8 as a file? that still a quotes
problem,
On Fri, 10 Apr 2009, Andy Wong wrote:
Yes, if leave a space between the last two quotes, mtx output seems ok.
MTXrun |
MTXrun | executing: vim -u NONE -c set tabstop=8 test.tex
MTXrun |
But it still cause vim open two file named tabstop=8 and test.tex to
edit. So it seems vim treat tabstop=8
It may be windows has problem to handle the space in quoted parameters?
write those commands to a batch file then call by mtxrun works right. May be
it is a solution. :)
Andy
On Fri, Apr 10, 2009 at 3:32 PM, Aditya Mahajan adit...@umich.edu wrote:
On Fri, 10 Apr 2009, Andy Wong wrote:
Yes,
I get this error:
...text/tex/texmf-context/tex/context/base/font-syn.lua:12: attempt to
index global 'tex' (a nil value)
I just commented out this line, and it seems to be working OK so fare.
Regards,
Khaled
--
Khaled Hosny
Arabic localiser and member of Arabeyes.org team
Free font
With
$ export TEXINPUTS=.:/home/local/tex//:
mtxrun fails
$ mtxrun --script fonts --list
cannot open : No such file or directory
as it looks to open /home/local/tex/font-syn.lua
rather than /usr/share/texmf/tex/context/base/font-syn.lua
(after succeeding to find
Patrick Gundlach wrote:
Hi,
...k/TeX/context/minimal/tex/texmf-osx-intel/bin/mtxrun:6898: attempt
to index local 'files' (a nil value)
what does that mean? Is the syntax I've used correct?
Update the script with mtxrun --selfupdate.
That's cool, it works nicely. Thanks!
there's also
Hi,
I tried to find a tfm file, so I typed in
~$ mtxrun --locate texnansi-demofont.tfm
and I got
...k/TeX/context/minimal/tex/texmf-osx-intel/bin/mtxrun:6898: attempt
to index local 'files' (a nil value)
what does that mean? Is the syntax I've used correct?
Patrick
--
ConTeXt wiki and
Am 24.08.2008 um 12:44 schrieb Patrick Gundlach:
Hi,
I tried to find a tfm file, so I typed in
~$ mtxrun --locate texnansi-demofont.tfm
and I got
...k/TeX/context/minimal/tex/texmf-osx-intel/bin/mtxrun:6898: attempt
to index local 'files' (a nil value)
what does that mean? Is the
Hi,
...k/TeX/context/minimal/tex/texmf-osx-intel/bin/mtxrun:6898: attempt
to index local 'files' (a nil value)
what does that mean? Is the syntax I've used correct?
Update the script with mtxrun --selfupdate.
That's cool, it works nicely. Thanks!
Patrick
--
ConTeXt wiki and more:
Hi
sudo ./first-setup.sh
I always update the context minimals in this way, so I have never
heard about this problem:(
Yue Wang
___
If your question is of interest to others as well, please add an entry to the
2008/8/9 Mojca Miklavec [EMAIL PROTECTED]:
This error occurrs on a Mac G5 (PPC) running OSX 10.4; ConTeXt
is installed in /usr/local/ConTeXt.
Thanks for the other hint about PPC. Can you please retry the installation?
All is well again, thank you!
Greetlings, Hraban
On Fri, Aug 8, 2008 at 4:15 AM, Henning Hraban Ramm [EMAIL PROTECTED] wrote:
For I had some problems with my installation I tried to start from
scratch. But I'm stuck with an error in mtxrun:
Welcome to Darwin!
user$ cd /usr/local/ConTeXt/
/usr/local/ConTeXt user$ rsync -ptv
On Sat, Aug 9, 2008 at 1:09 AM, Henning Hraban Ramm [EMAIL PROTECTED] wrote:
Am 2008-08-08 um 23:38 schrieb Hans Hagen:
Henning Hraban Ramm wrote:
Line 1741 of mtxrun contains a popen command to execute a system
command; but even if I change that (e.g. printing the accessed
variable before),
For I had some problems with my installation I tried to start from
scratch. But I'm stuck with an error in mtxrun:
Welcome to Darwin!
user$ cd /usr/local/ConTeXt/
/usr/local/ConTeXt user$ rsync -ptv
rsync://contextgarden.net/minimals/setup/first-setup.sh .
first-setup.sh
sent 115 bytes received
Henning Hraban Ramm wrote:
Line 1741 of mtxrun contains a popen command to execute a system
command; but even if I change that (e.g. printing the accessed
variable before), the error stays at that line, so the message is
probably wrong.
what mtxrun do you run ... you need to copy the file
Am 2008-08-08 um 23:38 schrieb Hans Hagen:
Henning Hraban Ramm wrote:
Line 1741 of mtxrun contains a popen command to execute a system
command; but even if I change that (e.g. printing the accessed
variable before), the error stays at that line, so the message is
probably wrong.
what
On 17 jun 2008, at 21:47, Aditya Mahajan wrote:
On Tue, 17 Jun 2008, Hans van der Meer wrote:
Following the article The luafication of TeX and Context in the
recent issue of the NTG-MAPS I tried the example given:
mtxrun --script fonts
and this should return the options list for this
Hans van der Meer wrote:
On 17 jun 2008, at 21:47, Aditya Mahajan wrote:
On Tue, 17 Jun 2008, Hans van der Meer wrote:
Following the article The luafication of TeX and Context in the
recent issue of the NTG-MAPS I tried the example given:
mtxrun --script fonts
and this should return
Hi Hans,
Hans van der Meer wrote:
So, I am still stuck with
cannot open : No such file or directory.
on calling 'mtxrun --script fonts' etc.
I should have tried this myself instead of attempting to guess. :-(
The problem is this line in mtx-fonts.lua:
Following the article The luafication of TeX and Context in the
recent issue of the NTG-MAPS I tried the example given:
mtxrun --script fonts
and this should return the options list for this script.
However, I get:
101 ~: mtxrun --script fonts
cannot open : No such file or
Hans van der Meer wrote:
Following the article The luafication of TeX and Context in the
recent issue of the NTG-MAPS I tried the example given:
mtxrun --script fonts
and this should return the options list for this script.
However, I get:
101 ~: mtxrun --script fonts
On Tue, 17 Jun 2008, Hans van der Meer wrote:
Following the article The luafication of TeX and Context in the
recent issue of the NTG-MAPS I tried the example given:
mtxrun --script fonts
and this should return the options list for this script.
However, I get:
101 ~: mtxrun
Hello,
I still can't run
mtxrun --scripts fonts --mtxrun --reload the output give me :
MtxRun | unknown script: fonts
I tried with my context installation in /usr/share/texmf and with
context minimal.
Digging in my directories, I supose that thoses scripts are the mtx-*
in
On Wed, Apr 16, 2008 at 12:07 PM, Olivier Guéry [EMAIL PROTECTED] wrote:
Hello,
I still can't run
mtxrun --scripts fonts --mtxrun --reload the output give me :
MtxRun | unknown script: fonts
mtxrun --scripts fonts --reload
I tried with my context installation in /usr/share/texmf and with
Thank's I find the problem reading to another post.
I had a TEXMF variable set to /usr/share/texmf
I unset it and it seems that mtxrun go well.
But strange isn't it ?
Olivier.
___
If your question is of interest to
Olivier Guéry wrote:
Thank's I find the problem reading to another post.
I had a TEXMF variable set to /usr/share/texmf
I unset it and it seems that mtxrun go well.
But strange isn't it ?
the problem can be that some distributions have hard coded paths and use
autofoo and autoparentfoo magic
101 - 152 of 152 matches
Mail list logo
