Le 05/11/2010 14:22, Taco Hoekwater a écrit :
> I could have sworn this was
> mentioned in the manual, but I cannot find it myself either.
Got it! It was in the manual under buildpage_filter for luatex 0.25:
> As for all the callbacks that deal with nodes, the return value can be one of
> three
Le 05/11/2010 14:57, Taco Hoekwater a écrit :
> On 11/05/2010 02:56 PM, Manuel Pégourié-Gonnard wrote:
>> Le 05/11/2010 14:52, Taco Hoekwater a écrit :
>>> On 11/05/2010 02:46 PM, Manuel Pégourié-Gonnard wrote:
>>>> Le 05/11/2010 14:22, Taco Hoekwater a écrit :
>&
Le 05/11/2010 14:52, Taco Hoekwater a écrit :
> On 11/05/2010 02:46 PM, Manuel Pégourié-Gonnard wrote:
>> Le 05/11/2010 14:22, Taco Hoekwater a écrit :
>>> In all these cases the result of returning a boolean is the same:
>>>
>>> false == callback has failed
Hi,
[btw: I meant to write to the users list, sorry]
Le 05/11/2010 14:22, Taco Hoekwater a écrit :
> In all these cases the result of returning a boolean is the same:
>
>false == callback has failed
>true == callback has run ok, but nothing has been changed
>
> the latter case (true) is
Hi,
Sorry if this is very clear from the manual, maybe I just didn't read the part
where it is explained (or I read it but was too stupid/tired to notice), but I
don't understand the meaning of the return value of some callbacks.
The first example (by order of apparition in the manual) is
pre_lin
Le 24/04/2010 14:32, Manuel Pégourié-Gonnard a écrit :
I suggest the attached patch
Did I write "attached"?
m
diff --git a/build.sh b/build.sh
index 94e6421..549e288 100755
--- a/build.sh
+++ b/build.sh
@@ -8,8 +8,11 @@
# --make : only make, no make distclean;
Hi Taco,
While trying to cross-compile luatex from linux to win32 using mingw, I got a
failure due to the --host setting not matching what is installed on my machine.
I changed that in build.sh and got a second, but less serious error, about
mingw32-strip no being found.
I suggest the attach
Hi Tomek,
T T a écrit :
> On 22 April 2010 00:03, Manuel Pégourié-Gonnard wrote:
>> Yeah, that's really amazing. Maybe something with the environment that would
>> propagate differently using spawn/exec vs execute?
>
> Manuel, you've been on the right track all a
Taco Hoekwater a écrit :
> I have just uploaded the archives for a new luatex release, 0.60.0.
>
> This release starts a new chain of stable beta's, and will be the
> version included in this year's TeXLive.
>
Great news! Many thanks.
Sorry for nitpicking, but:
> * There are new functions node.
Hi,
T T a écrit :
> I've noticed that os.execute under texlua echos its argument to
> stderr. This is not the behaviour under the standard lua interpreter.
> Is it a bug or feature (and what would be the reason for it)?
>
Which version of texlua? I don't observe this behaviour with texlua
0.40.6
Hi Reinhard,
Reinhard Kotucha a écrit :
>kpse.set_program_name('ppower4')
The problem is that kpse resolves symlinks before computing SELFAUTO*
(which is what you want in most cases). So SELFAUTOLOC ends up being
texmf-dist/scripts/ppoxer4 which obviously gives the wrong result.
A general ap
Hi,
Here's a small problem with luatex from trunk (notice the missing 'hello' in the
first line):
! \csname\endcsname.
l.2 \errmessage{hello \csname\endcsname}
More generally, print_cs() screws things up when printing null_cs while selector
is new_string, by indirectly calling make_string(). I t
Khaled Hosny a écrit :
> Any news about this man page, I assumed it was OK since there were no
> further complaints :) but now texlive2009 pretest is out and I see the
> old man page.
>
I assume we were waiting for further comments and forgot to install it. I'll
install the new man page tonight (r
Nicola a écrit :
> luatex -ini luatex.ini dump
>
> and I get
>
> This is LuaTeX, Version beta-0.40.6-2009062619 (Web2C 2009) (INITEX)
> (/usr/local/texlive/2008/texmf-dist/tex/plain/config/luatex.ini
> (/usr/local/texlive/2008/texmf-dist/tex/plain/config/etex.ini
> (/usr/local/texlive/2008/texmf-
Manuel Pégourié-Gonnard a écrit :
> While trying to tangle luatex.web, I found it necesseary to apply the
> following
> patch in order to fix what looks like two typos.
>
By the way, while pdfluatex-ing the result, I noticed problems with naked
\outputbox in the text, for w
Hi,
While trying to tangle luatex.web, I found it necesseary to apply the following
patch in order to fix what looks like two typos.
diff --git a/source/texk/web2c/luatexdir/luatex.web
b/source/texk/web2c/luatexdir/luatex.web
index bfcf025..5f0eb64 100644
--- a/source/texk/web2c/luatexdir
Taco Hoekwater a écrit :
> I'll think about this some more, but just going back to whatever
> web2c was doing just because that was what web2c was doing, may not
> such a good solution. Perhaps we could backport the braced filename
> support to the rest of web2c ...
>
By the way, if you backport b
Hans Hagen a écrit :
>> \input\jobname.myextention...
>
> well, in luatex that's ok then
Hum, unless I'm mistaken that's not ok because while compiling 'foo bar.tex',
you get
\input foo bar.tex
which is likely to complain about a missing foo.tex file.
> but if pdftex adds "" you'd get \input
>
Taco Hoekwater a écrit :
> There is a consistency problem with the web2c extension that handles
> filename quoting, yes. I have removed the quotes recently after it
> became obvious that the quoting mechanism in web2c does not know how
> to deal with directory separators in font file names properly
Hi,
Consider the following source file
\edef\x{\jobname}
\show\x
Run it with pdftex, you get:
> \x=macro:
->"foo bar".
With luatex (0.40):
> \x=macro:
->foo bar.
This is a problem eg when using LaTeX when it tries to \input\jobname.aux.
Regardless of any particular format, there is a consis
Taco Hoekwater a écrit :
> * Maybe point to either www.luatex.org or to "texdoc luatex"
> (although I am not certain that that actually works)
>
In current TeX Live (2008 with updates), 'texdoc luatex' opens luatexref-t.pdf.
> I believe that the current consensus these days is that it is better
[un-cc-ing the metapost list since this part is only about luatex]
Khaled Hosny a écrit :
> OK, here is a more or less working man page, based on pdftex.man and
> luatex.1 from Debian.
Cool, thanks!
> I omitted some options from pdftex man page that
> I'm not sure are supported by luatex, includ
Khaled Hosny a écrit :
> On Tue, Apr 21, 2009 at 11:50:24PM +0200, Taco Hoekwater wrote:
>>> PS: do you plan to provide a man page for luatex in the future?
>> Not an exhaustive one for sure, but maybe a generic one that just
>> lists the commandline switches and points to the manual (like
>> pdfte
David Kastrup a écrit :
>> So `#' is transformed into `##' when passed from TeX to Lua.
>
> No, when TeX prints.
>
>> Is this a bug or a feature?
>
> Feature. Quite an annoying one in my opinion, but there you are.
>
By the way, using LaTeX, the "ted" package has a command \ShowTokens
which is
Hans Hagen a écrit :
> i tried your script
You mean scriptS? Because the problem happens only when there are two
scripts involved.
I did another round of tests, systematically trying all combinations of
os.execute, os.exec, os.spawn, with both string and list form for exec
and spawn. The result i
Hans Hagen scripsit (02.09.2008 10:09)
> can you try the table call, like in
>
> os.exec({"c:\\Program Files\\Adobe\\Reader
> 9.0\\Reader\\acrord32.exe","e:/tmp/oeps.pdf"})
>
I did try the table call (that's actually the form used in the original script
where the problem first appeared).
> here
Hi Taco, hi Hans, hi everyone,
With LuaTeX 0.25.4 from the TeX Live distribution, I get a strange
behaviour when, in a texlua script, I call another texlua script which
in turn calls a program, depending on the sequence os.spawn and/or
os.execute I use.
Example, assuming acrord32 is in the PATH a
Hi,
I just tried the following:
[EMAIL PROTECTED]:~% echo '\\bye' > foobar
[EMAIL PROTECTED]:~% pdftex foobar
This is pdfTeXk, Version 3.1415926-1.40.9 (Web2C 7.5.7)
%&-line parsing enabled.
entering extended mode
(./foobar )
No pages of output.
Transcript written on foobar.log.
[EMAIL PROTECTED
28 matches
Mail list logo
