On 2014-09-12, 2:40, Kip Warner wrote:
I'd like to write a short scientific paper describing an algorithm I
discovered in the realm of computational geometry a few years ago
before I forget it entirely. I've been meaning to do this for some
time, but haven't had a chance. I'd like to use
Dear Developers and All,
lpdf.checkedkey routine from lpdf-ini.lua has problems with accessing
false boolean values, it returns them as nil. Is it by design or
neglect?
(I vaguely remember stumbling on this problems before, so there is a
chance that I have already got the answer, but have
Am 15.09.2014 um 16:14 schrieb Michail Vidiassov:
Dear Developers and All,
lpdf.checkedkey routine from lpdf-ini.lua has problems with accessing
false boolean values, it returns them as nil. Is it by design or
neglect?
More a lua design decision. 'nil' is equal to 'false' here, 'true' is
Dear Peter,
More a lua design decision. 'nil' is equal to 'false' here
I know no CS theory behind lua design, but try this:
\starttext
\startluacode
if nil == false then
io.write(nil == false\n)
end
if nil ~= false then
io.write(nil ~= false\n)
end
\stopluacode
TEST
\stoptext
and get
nil
On Mon, 15 Sep 2014, Michail Vidiassov wrote:
Dear Peter,
More a lua design decision. 'nil' is equal to 'false' here
I know no CS theory behind lua design, but try this:
\starttext
\startluacode
if nil == false then
io.write(nil == false\n)
end
if nil ~= false then
io.write(nil ~=
I'm writing a module to typeset problems/tests. Depending on a flag,
solutions are either displayed or not. If the solutions are not displayed,
I want to give a certain amount of empty vertical space for the student's
work. This is where my difficulty begins.
The typesetting works with the
Dear Aditya, Peter and All,
I think that what Peter meant was:
the real issue is not teaching me lua and improving the style of my example,
but my complaint (correct or not) about inability of lpdf.checkedkey
to correctly fetch false boolean values: they are fetched as nil, just
as if they were
On 9/15/2014 6:12 PM, Michail Vidiassov wrote:
Dear Aditya, Peter and All,
I think that what Peter meant was:
the real issue is not teaching me lua and improving the style of my example,
but my complaint (correct or not) about inability of lpdf.checkedkey
it looks like your question was
On Mon, 2014-09-15 at 15:18 +0200, Joshua Krämer wrote:
At the moment, I am writing my MD thesis using ConTeXt. I have
equations, figures, tables, diagrams, references. There is also Lua
code embedded to prepare data tables from CSV files, round values etc.
Of course, there is a lot in my
Dear Hans,
well, they're just not treated special
IMHO, they have to be treated special.
you can try this (untested)
I have tested it. It adds nice enhancement, but does not fix the bug
In the following case
local a = {}
a[e] = blabla
a[t] = true
a[f] = false
a[x] = true
a[y] = false
a[z] =
Dear list,
I have a simplified verson of the sample I submitted to the list almost
a week ago:
\setuppapersize[A8]
\starttext
\startlinenumbering
\hsize\zeropoint
sentence
sentence
sentence
\stoplinenumbering
\hsize\zeropoint
sentence
sentence
sentence
\stoptext
I’m afraid that line numbering
On 9/15/2014 8:25 PM, Michail Vidiassov wrote:
Dear Hans,
well, they're just not treated special
IMHO, they have to be treated special.
you can try this (untested)
I have tested it. It adds nice enhancement, but does not fix the bug
In the following case
local a = {}
a[e] = blabla
a[t] =
Dear Hans,
more like
function lpdf.checkedkey(t,key,variant)
thank you. That works. Please, commit.
Michail
PS.
lpdf.checkedkey issue was raised while I reviewed 3D PDF support.
But there are greater problems:
It seems that u3d inclusion stopped to work in the current (2014.09.06
20:59)
13 matches
Mail list logo
